-
Notifications
You must be signed in to change notification settings - Fork 26
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
Bump to kind 0.20.0 #1297
Bump to kind 0.20.0 #1297
Conversation
🤖 Created branch: z_pr1297/skitt/kind-0.20 |
Deployment (ovn) failed, re-running. |
Deployment (ovn) failed again. |
Deployment (ovn) failed again, seems to be consistent. |
@aswinsuryan the OVN cluster deployment seems to be failing. Do you have any idea of the recent changes in OVN repo?
|
The OVN job consistently fails in this PR (oddly with very little output - seems to timeout) but didn't fail in the dependabot bump PR. The difference is that this PR updates the hashes in scripts/shared/lib/clusters_kind. |
It may be solved when dfarrell07#55 goes in. The OVN image we use is an old one as it does get update in quay for every PR merged in OVN. With this one we building image with latest code. |
Ok but does that explain why the same job for #1333 succeeds? |
oh that is strange , I would expect it to be same. |
This PR also updated the |
I might be wrong, but AFAICT the dependabot updates the go dependencies, while this one updated the actual K8s env that gets deployed, hence the first one is fine while this one clearly has some issues with OVN (which might get fixed with Daniel's patch)
@dfarrell07 maybe based on this info we want to always rebuild the OVN image, not just on IC mode? |
Maybe after the OVN IC PR goes in we can rebase this to test it with both the rebuilt and old images. |
I think we need an owner to rebase this and resolve the conflicts to see it run with both the rebuilt OVN image and the old one. |
I rebased but it still fails. |
Since #1302, the Go dependencies determine the versions of tools we use (the idea being that dependabot then keeps track of updates for us). So #1333 also changes the version of kind deployed in the environment. Without the hash changes however, the k8s images being deployed don’t change. I haven’t checked in detail what the actual changes are, but as a general rule we’re supposed to use the hashes given with each kind release (because images are often rebuilt to handle changes in kind itself). |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
We're still seeing weirdness with OVN CI (K8s networkplugin doesn't come up). |
@aswinsuryan Can you please take a look at this one on priority. We need it to start testing k8s 1.28. |
71d8ff8
to
59281f7
Compare
The ovn-kube-node pod fails to come up due to this error.
It works fine with |
@aswinsuryan thanks for the investigation! Do you know what the fix needs to be? I haven’t found a difference between the 1.26.3 and 1.26.6 images which would explain the change in behaviour... |
This PR/issue depends on: |
I bumped ovn-kubernetes to the tip of the main branch, with the |
Now it is failing at,
we use the Adding this (in scripts/shared/lib/clusters_kind) solves it, but not sure if it is something we want to do
|
Adding |
This adds support for Kubernetes 1.28. ovn-kubernetes needs to be bumped to a version with support for the new Debian 11-based kind images (iptables is only in /usr/sbin). openssl is no longer available, which causes deployments to fail when trying to set up certificates for node identity; disable that for now (this might be fixed with Debian 12-based images in kind 0.21). Signed-off-by: Stephen Kitt <[email protected]>
🤖 Closed branches: [z_pr1297/skitt/kind-0.20] |
This adds support for Kubernetes 1.28.
Depends on ovn-kubernetes/ovn-kubernetes#4015