-
Notifications
You must be signed in to change notification settings - Fork 3k
Update CI to use more recent versions of Kubernetes in the relevant jobs #47775
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
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
Can't merge this, need an admin to do it |
CI seems stuck |
Openshift won't work. |
This brings the question as to whether this is indeed even worth testing on OpenShift if we can't check current versions. What do you think, @gsmet? |
Why can't I even check what's going on with the CI Sanity Check? |
Something seems to be stuck. I propose a rebase and force push |
69d3e54
to
8cf8511
Compare
Doesn't seem to be doing anything. |
No idea what the issue is |
It won't run CI as it's touching something that is not relevant to main CI. IIRC, this is only triggered with a schedule. |
And my understanding was that we were unable to test with recent OpenShift and that these workflows were kinda outdated (I raised the problem a while ago). |
We still have IBM Cloud to perform these tests. I can set up a cluster with the latest OpenShift version if necessary |
What's the resolution on this? It would be good to start getting at plain Kube CI runs again… |
OpenShift-related versions cannot be updated at this point.
8b60381
to
ce67c29
Compare
This comment has been minimized.
This comment has been minimized.
Status for workflow
|
This updates the dependencies used in Kubernetes integration tests to more recent versions. Note that there doesn't seem to be a real recent, tagged version of OCP to use, at least, not that I could quickly figure out, without going hunting for it, so this might require some more work.