fix/update versions according to k8s Deprecated API Migration Guide #283
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
|
|
|
@chdorb Thanks for opening your first PR! 🎉 I'll get this to someone to review. |
lucasreed
approved these changes
Mar 1, 2022
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.
see https://kubernetes.io/docs/reference/using-api/deprecation-guide/
This PR fixes #282
Checklist
Description
What's the goal of this PR?
Update and add missing versions of k8s components according to the Kubernetes documentation Deprecated API Migration Guide
What changes did you make?
Update existing versions and add missing on the versions.yaml file.
What alternative solution should we consider, if any?