-
Notifications
You must be signed in to change notification settings - Fork 23
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
Update kubernetes packages #186
base: develop
Are you sure you want to change the base?
Conversation
Update to v1-31-eks-4.
Update to upstream v1-30-eks-15
Upstream v1-29-eks-22
Update to upstream v1-28-eks-33
Update to 1.27.16
Add upstream patch 0016.
Add patch 0025
Add upstream patch 0037
Six advisories: two vulnerabilites each in three kubernetes packages, kubernetes-1.27, kubernetes-1.28, and kubernetes-1.29.
A little more detail on the advisories: these are all vulnerabilities from govulncheck. One is rated High, one Low. The CVE descriptions are a little misleading. Both CVEs talk about |
The severity ratings for the advisories came from NVD (the high-severity CVE) and GitHub (the low-severity CVE). NVD hasn't analyzed the low-severity CVE yet. High severity: container can open arbitrary things on the host. Low severity: container can create new empty files and directories on the host (but can't overwrite existing files). |
Description of changes:
Updates kubernetes-1.24 through 1.31 to the latest upstream versions. Moves kubernetes-1.27 from standard support to extended.
Testing done:
Built AMIs, created nodegroups with eksctl, verified that they would each join the cluster and run busybox. Accidentally verified that an aws-k8s-1.31 node will not join a v1.30 cluster, but will join a v1.31 cluster.
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.