[tls-scanner] Provision 4.22 cluster for default-tls test step#75334
[tls-scanner] Provision 4.22 cluster for default-tls test step#75334richardsonnick wants to merge 1 commit intoopenshift:mainfrom
Conversation
|
Skipping CI for Draft Pull Request. |
2171623 to
7f36e82
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: richardsonnick The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
I proposed something similar in #75394 - but it also updates the periodic job. |
| test: | ||
| - ref: tls-scanner-run | ||
| workflow: generic-claim | ||
| workflow: ipi-aws |
There was a problem hiding this comment.
Yep let's use that!
|
@richardsonnick: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
The default-tls conformance ci step attempts to claim a 4.22 cluster, yet that version does not exist in the cluster pool atm.
This diff provisions a new 4.22 cluster for the default-tls test step, similar to the tls13-conformance test.