Page MenuHomeSoftware Heritage
Create Task
Maniphest T4358

Upgrade AKS versions
Closed, MigratedEdits Locked
Actions

Description

Email received from azure:

Upgrade your AKS cluster to a supported Kubernetes version

You're receiving this notice because you currently use Azure Kubernetes Service (AKS).

AKS is retiring v1.21.x on 31 July 2022. We've detected that one or more AKS clusters in your subscription(s) are using Kubernetes v1.21.x or lower. To stay within supported versions and service-level agreements (SLA) you have up to 30 days after the version is removed to upgrade. To avoid ever falling out of support and to keep up with Kubernetes versions, we recommend turning on auto-upgrade.
Recommended action

Please upgrade your clusters to 1.22.x or higher by 31 July 2022.
More information

    To keep up to date with all AKS releases, subscribe to the AKS Releases page.
    To know when the next versions will be introduced or retired, check the Kubernetes release calendar for AKS.

If you have questions, get answers from community experts in Microsoft Q&A. If you have a support plan and you need technical help, please contact us.
Account Information

Subscription ID: <redacted>
Subscription name: <redacted>
Resource group: EUWEST-GITLAB-STAGING
Cluster name: EUWEST-GITLAB-STAGING

Subscription ID: <redacted>
Subscription name: <redacted>
Resource group: EUWEST-RANCHER
Cluster name: EUWEST-RANCHER

Related Objects
Search...

Event Timeline

vsellier changed the task status from Open to Work in Progress.Jun 29 2022, 9:45 AM
vsellier triaged this task as Normal priority.
vsellier created this task.
vsellier moved this task from Backlog to in-progress on the System administration board.
vsellier added a comment.Jun 29 2022, 9:54 AM

It seems the rancher cluster can be updated to any version :
from https://rancher.com/docs/rancher/v2.6/en/installation/install-rancher-on-k8s/:

Rancher can be installed on any Kubernetes cluster. This cluster can use upstream Kubernetes, or it can use one of Rancher’s Kubernetes distributions, or it can be a managed Kubernetes cluster from a provider such as Amazon EKS.

It's also confirmed by the suse rke compatibility matrix: https://www.suse.com/assets/EN-Rancherv2.6.4-150422-0151-56.pdf

The gitlab operatar is officially compatible until kubernetes 1.21.
But according https://gitlab.com/groups/gitlab-org/-/epics/6883#api-removals-for-kubernetes-v122, it seems it should not have a lot of impacts to migrate to 1.22.
It will be checked on the rancher cluster

vsellier changed the status of subtask T4359: Update rancher cluster to kubernetes 1.22 from Open to Work in Progress.Jul 7 2022, 6:22 PM
vsellier closed subtask T4359: Update rancher cluster to kubernetes 1.22 as Resolved.Jul 7 2022, 6:37 PM
vsellier added a comment.Oct 5 2022, 2:24 PM

Looks like the gitlab operator is now compatible with kubernetes 1.22.
https://docs.gitlab.com/operator/installation.html#kubernetes

vsellier closed this task as Resolved.Oct 7 2022, 9:08 AM
vsellier closed subtask T4360: Update gitlab kubernetes cluster to 1.22 as Resolved.
vsellier moved this task from in-progress to done on the System administration board.
gitlab-migration changed the task status from Resolved to Migrated.Oct 19 2022, 6:07 PM
gitlab-migration claimed this task.
gitlab-migration added a subscriber: gitlab-migration.

This task has been migrated to GitLab.

gitlab-migration changed the status of subtask T4359: Update rancher cluster to kubernetes 1.22 from Resolved to Migrated.Oct 19 2022, 6:07 PM
gitlab-migration changed the status of subtask T4360: Update gitlab kubernetes cluster to 1.22 from Resolved to Migrated.
About · Developer information · Legal