-
Notifications
You must be signed in to change notification settings - Fork 566
Add support for kubernetes 1.34 #4416
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
base: main
Are you sure you want to change the base?
Conversation
.chloggen/eks134.yaml
Outdated
| component: operator | ||
|
|
||
| # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). | ||
| note: Support for Kubernetes `1.34` version. |
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.
| note: Support for Kubernetes `1.34` version. | |
| note: Support for Kubernetes `1.34` version. |
pavolloffay
left a comment
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.
Please fix the @frzifus comment
|
I am restarting the failed CI job |
|
unit test failed again, they are probably flaky |
Head branch was pushed to by a user without write access
|
@vasireddy99 the CI is still failing. Did you try running the basic checks locally? |
swiatekm
left a comment
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.
These envtest failures look legit to me. We might be doing something wrong that is only now surfaced by running on 1.34. Considering E2E tests are green, I'd expect the problem lie more in our envtest setup. Either way, we can't merge with all of these failing.
Description: Add support for kubernetes 1.34
Resolves #4415