Drop k8s 1.26 metal and VMWare variants #4018
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This removes the metal and VMware 1.26 variants. This version of Kubernetes has gone end-of-life and these variants are no longer supported. Signed-off-by: Gavin Inglis <giinglis@amazon.com>
yeazelm
approved these changes
May 31, 2024
Signed-off-by: Gavin Inglis <giinglis@amazon.com>
bcressey
approved these changes
Jun 1, 2024
yeazelm
approved these changes
Jun 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue number:
Closes #4017
Description of changes:
This removes the metal and VMware 1.26 variants. This version of Kubernetes has gone end-of-life upstream in February of 2024, will go end-of-life in EKS in mid-June, and these variants are no longer supported.
Also, add missing docs for k8s 1.30 variants.
Testing done:
Build succeeds.
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.