-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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 minimum-supported K8s version to v1.20 #7172
Merged
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
Kubernetes v1.19 is reaching its end-of-life date on 2021-10-28. In anticipation of this, we should explicitly update our minimum supported version to v1.20. This allows us keep our dependencies up-to-date and ensures that we can actually test against our minimum supported version. Fixes #7171
olix0r
changed the title
Update minimunm-supported K8s version to v1.20
Update minimum-supported K8s version to v1.20
Oct 28, 2021
Merged
alpeb
approved these changes
Oct 28, 2021
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.
@olix0r I took the liberty of pushing some missing parts, in particular the minimal k8s version the healthcheck checks for.
@alpeb thank you :) |
adleong
approved these changes
Oct 28, 2021
olix0r
added a commit
that referenced
this pull request
Mar 31, 2022
Kubernetes v1.19 is reaching its end-of-life date on 2021-10-28. In anticipation of this, we should explicitly update our minimum supported version to v1.20. This allows us keep our dependencies up-to-date and ensures that we can actually test against our minimum supported version. Fixes #7171 Co-authored-by: Alejandro Pedraza <alejandro@buoyant.io> (cherry picked from commit c88c0ed) Signed-off-by: Oliver Gould <ver@buoyant.io>
olix0r
added a commit
that referenced
this pull request
Apr 7, 2022
Kubernetes v1.19 is reaching its end-of-life date on 2021-10-28. In anticipation of this, we should explicitly update our minimum supported version to v1.20. This allows us keep our dependencies up-to-date and ensures that we can actually test against our minimum supported version. Fixes #7171 Co-authored-by: Alejandro Pedraza <alejandro@buoyant.io> (cherry picked from commit c88c0ed) Signed-off-by: Oliver Gould <ver@buoyant.io>
olix0r
added a commit
that referenced
this pull request
Apr 8, 2022
Kubernetes v1.19 is reaching its end-of-life date on 2021-10-28. In anticipation of this, we should explicitly update our minimum supported version to v1.20. This allows us keep our dependencies up-to-date and ensures that we can actually test against our minimum supported version. Fixes #7171 Co-authored-by: Alejandro Pedraza <alejandro@buoyant.io> (cherry picked from commit c88c0ed) Signed-off-by: Oliver Gould <ver@buoyant.io>
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.
Kubernetes v1.19 is reaching its end-of-life date on 2021-10-28. In
anticipation of this, we should explicitly update our minimum supported
version to v1.20. This allows us keep our dependencies up-to-date and
ensures that we can actually test against our minimum supported version.
Fixes #7171