-
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 #7171
Labels
priority/P0
Release Blocker
Milestone
Comments
olix0r
added a commit
that referenced
this issue
Oct 28, 2021
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
This was referenced Oct 28, 2021
olix0r
added a commit
that referenced
this issue
Oct 28, 2021
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>
olix0r
added a commit
that referenced
this issue
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 issue
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 issue
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Linkerd's minimum supported k8s version is currently v0.17. Kubernetes v1.19 is due to reach its end-of-life... tomorrow (2021-10-28) per https://kubernetes.io/releases/patch-releases/#1-19. v1.17 reached its EOL date on 2021-01-13.
Using such an old version of the kubernetes API prevents us from updating dependencies (e.g. #7170, #6698) and causes Linkerd installs to emit deprecation warnings. Also, it's extremely difficult to provision clusters with EOL k8s versions in integration tests (#7112).
In the short term, we should update our minimum supported version to v1.20. Generally, as a project, we should only commit to updating our minimum supported version to avoid maintaining support for EOL'd versions. v1.20 will be EOL'd on 2022-02-28...
The text was updated successfully, but these errors were encountered: