-
Notifications
You must be signed in to change notification settings - Fork 735
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
v1.12 Helm chart changes and release manifests #2122
Conversation
Changes LGTM. Can you also update the README in the root directory to reflect the dockershim removal? The "Container Runtime" section, that is |
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 but we need to update the readme - https://github.com/aws/amazon-vpc-cni-k8s#container-runtime
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.
Please call out on the readme that this cannot be utilized with older versions of CNI.
updated the readme about container runtime :D |
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
A post merge comment. Can we prevent installation of these in < EKS 1.24 cluster. |
* v1.12 Helm chart changes and release manifests * update readme for container runtime * update readme for container runtime
What type of PR is this?
release
Which issue does this PR fix:
N/A
What does this PR do / Why do we need it:
This PR adds the release manifests and helm changes for v1.12
The helm chart version was bumped to v1.2.0 since we no longer have CRI mounts since CNI v1.12
If an issue # is not available please add repro steps and logs from IPAMD/CNI showing the issue:
Testing done on this change:
Manually tested canary tests with generated YAML.
Automation added to e2e:
Will this PR introduce any new dependencies?:
Will this break upgrades or downgrades. Has updating a running cluster been tested?:
Yes. This helm chart is only compatible with CNI version >= v1.12
Does this change require updates to the CNI daemonset config files to work?:
Yes, the CNI's CRI mount is removed. Since CNI v1.12, we switched to use state file instead of rely on CRI mount.
Does this PR introduce any user-facing change?:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.