Support deploying GitLab on Kubernetes 1.26
Support deploying GitLab on Kubernetes 1.26
Summary
Kubernetes 1.26 includes deprecations and removals we need to consider before verifying GitLab installation on that version.
https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-26
This Epic will track the changes we need to make to ensure compatibility.
For Kubernetes 1.25, see &7599 (closed).
For Kubernetes 1.27, see &11320 (closed).
- Show closed items
- View on a roadmap
- Issuegitlab-org/cloud-native/gitlab-operator#127016.6Deliverable OpenShift devops systems group distribution maintenance pipelines priority 3 quad-planning complete-no-action section core platform type maintenance workflow complete
- Issuegitlab-org/cloud-native/gitlab-operator#132916.4Deliverable Distribution KR 2 Distribution OBJ 1 FY24 Q2 For Scheduling devops systems group distribution group::distribution build maintenance pipelines priority 2 quad-planning complete-action section core platform severity 2 type maintenance workflow complete
- Issuegitlab-org/cloud-native/gitlab-operator#138116.9Deliverable devops systems group distribution maintenance pipelines priority 2 section core platform type maintenance
- Issuegitlab-org/charts/gitlab#489016.5Deliverable devops systems group distribution group::distribution build maintenance pipelines priority 3 quad-planning complete-no-action section core platform severity 3 type maintenance workflow complete
- Issuegitlab-org/charts/gitlab#488916.5Deliverable devops systems group distribution group::distribution build maintenance pipelines priority 2 quad-planning complete-no-action section core platform severity 2 type maintenance
- Show labels
- Show closed items
Related to
- Epic#11047Aug 18, 2023 – Jan 12, 2024Distribution KR 1 Distribution OBJ 2 FY24 Q3 devops systems group distribution section core platform
Activity
I'm not opposed to that - maybe we can decide based on the work required. We can start creating issues based on what changes are required, and split out into child Epics for Operator and Charts if it makes sense.
Since the Operator deploys the Charts under the hood, they're tightly coupled already - and oftentimes the Operator gets fixes for "free" when they're fixed in the Charts without any additional changes required.