Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[FEATURE REQUEST] Upgrade Kubernetes to 1.22.x #2660

Closed
12 of 13 tasks
atsikham opened this issue Oct 4, 2021 · 3 comments
Closed
12 of 13 tasks

[FEATURE REQUEST] Upgrade Kubernetes to 1.22.x #2660

atsikham opened this issue Oct 4, 2021 · 3 comments
Assignees
@atsikham @przemyslavic
Labels
area/kubernetes type/upgrade Task related to component upgrade

Comments

@atsikham
Copy link
Contributor

atsikham commented Oct 4, 2021 •
edited by seriva
Loading

Is your feature request related to a problem? Please describe.
Upgrade K8s to 1.22.x to be able to perform future upgrades.

Describe the solution you'd like
Upgrade K8s to 1.22.x with dependencies: CNI plugins, dashboard, etc. Check release notes for that, deprecated things should be removed/updated.

Additional information
The Kubernetes project maintains release branches for the most recent three minor releases (1.22, 1.21, 1.20). Kubernetes 1.19 and newer receive approximately 1 year of patch support. Kubernetes 1.18 and older received approximately 9 months of patch support.

DoD checklist

  • Changelog updated
  • COMPONENTS.md updated / doesn't need to be updated
  • Schema updated / doesn't need to be updated
  • Feature has automated tests
  • Automated tests passed (QA pipelines)
    • apply
    • upgrade
  • Idempotency tested
  • Documentation added / updated / doesn't need to be updated
  • All conversations in PR resolved
  • Solution meets requirements and is done according to design doc
  • Usage compliant with license
  • Backport tasks created / doesn't need to be backported
This was referenced Oct 4, 2021
Closed
Closed
@rafzei rafzei added type/upgrade Task related to component upgrade and removed status/grooming-needed labels Oct 11, 2021
@atsikham
Copy link
Contributor Author

https://kubernetes.io/docs/reference/config-api/kubeadm-config.v1beta3/#migration-from-old-kubeadm-config-versions

@rafzei rafzei mentioned this issue Dec 3, 2021
Closed
18 tasks
@rafzei
Copy link
Contributor

rafzei commented Dec 3, 2021 •
edited
Loading

Added #2659 as a blocker.

@atsikham atsikham self-assigned this Dec 10, 2021
@przemyslavic przemyslavic self-assigned this Dec 15, 2021
@przemyslavic
Copy link
Collaborator

przemyslavic commented Dec 28, 2021 •
edited
Loading

✔️ apply x86_64, aarch64
✔️ apply HA cluster
✔️ promote to HA
✔️ single machine installation
✔️ upgrade from v1.0 x86_64
✔️ upgrade from v1.1 aarch64
✔️ upgrade from v1.0 single machine installation
✔️ upgrade from v1.0 HA installation

Istio and Vault applications are not supported.

@seriva seriva closed this as completed Dec 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@atsikham atsikham

@przemyslavic przemyslavic

Labels
area/kubernetes type/upgrade Task related to component upgrade
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@atsikham @seriva @rafzei @przemyslavic