-
Notifications
You must be signed in to change notification settings - Fork 13
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
Add ocp 4.8.2 cli support for ci against ocp 4.8 #360
Conversation
e1bd621
to
8f68ef3
Compare
f679c6f
to
ac91bfe
Compare
ac91bfe
to
bd4ca0c
Compare
This PR stemmed from this JIRA task: ONYX-11430. Essentially, Infra wanted a test file that would test a set of projects against the OCP NEXT cluster. |
bd4ca0c
to
e7c91b4
Compare
- Add ocp 4.8.2 cli - Prefix secretless image with docker.io so that docker hub images can be pulled in ocp. This will resolve image pull issues with conjur-authn-k8s-client > IMPORTANT: the docker.io prefix is significant and impacts the conjur-authn-k8s-client when testing against ocp next (this will resolve the image pull error there as well)
e7c91b4
to
efcc326
Compare
Code Climate has analyzed commit efcc326 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 87.5% (0.0% change). View more on Code Climate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
What does this PR do?
What's changed? Why were these changes made?
Added cli support for testing against OCP 4.8 by implementing v4.8.2 for the cli. Using older 3.* cli threw exceptions
when describing k8s resources in openshift.
How should the reviewer approach this PR, especially if manual tests are required?
Are there relevant screenshots you can add to the PR description?
N/A
What ticket does this PR close?
Resolves ONYX-11430
Checklists
Change log
Test coverage
This PR includes new unit and integration tests to go with the code changes, or
The test against the OCP 4.8 (next) cluster is not new, per se, but has not been passing until these changes.
The changes in this PR do not require tests
Documentation
README
s) were updated in this PR, and/or there is a follow-on issue to update docs, or