Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DO NOT MERGE: Add support for running acceptance test on Openshift cluster #4369

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

NiniOak
Copy link
Contributor

@NiniOak NiniOak commented Sep 25, 2024

Changes proposed in this PR

  • Extending our testing to add support for running our nightly acceptance test on Microshift cluster that support openshift client
  • Add Openshift acceptance workflow to test suite

How I've tested this PR

CI must

  • Install Openshift Client & Kubectl
  • Install and Run Microshift
  • Install Consul
  • Run a sunset of tests to see supportability

How I expect reviewers to test this PR

See relevant CI steps

Checklist

@NiniOak NiniOak added pr/no-backport signals that a PR will not contain a backport label pr/no-changelog PR does not need a corresponding .changelog entry labels Sep 25, 2024
@NiniOak NiniOak changed the title NO NOT MERGE: Adding support for running acceptance test on Microshift cluster DO NOT MERGE: Adding support for running acceptance test on Microshift cluster Sep 25, 2024
@NiniOak NiniOak force-pushed the anita/openshift_testing_ci branch 4 times, most recently from fae7ec9 to 91f01a4 Compare October 1, 2024 15:41
@NiniOak NiniOak changed the title DO NOT MERGE: Adding support for running acceptance test on Microshift cluster DO NOT MERGE: Add support for running acceptance test on Microshift cluster Oct 3, 2024
@NiniOak NiniOak changed the title DO NOT MERGE: Add support for running acceptance test on Microshift cluster DO NOT MERGE: Add support for running acceptance test on Openshift cluster Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/no-backport signals that a PR will not contain a backport label pr/no-changelog PR does not need a corresponding .changelog entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant