You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,16 @@ Does not include:
19
19
-`readyz` and `healthz`
20
20
- Kubernetes Client with self authorization by `inClusterConfig`
21
21
22
+
## Version Compatibility
23
+
24
+
The minor versions of `cloud-provider-stackit` are specifically aligned with the minor versions of `kubernetes/kubernetes`. To ensure compatibility, you must use the cloud provider release that matches your cluster's Kubernetes minor version.
Copy file name to clipboardExpand all lines: docs/release-procedure.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,8 @@
6
6
-[General Information](#general-information)
7
7
-[Automated Release Process (Primary Method)](#automated-release-process-primary-method)
8
8
-[Manual Release Process (Fallback Method)](#manual-release-process-fallback-method)
9
+
-[Releasing a New Kubernetes Version](#releasing-a-new-kubernetes-version)
10
+
-[Remove a old Kubernetes Version](#remove-a-old-kubernetes-version)
9
11
10
12
## Overview
11
13
@@ -54,3 +56,13 @@ Publishing a new release triggers the same Prow release job that builds and publ
54
56
3. Create a new release branch `release-v1.XX` from `main`.
55
57
4. Update the Renovate configuration via a PR against `main`: add the new release branch to `baseBranchPatterns` and add a new rule in `packageRules` for `/^k8s.io/`. Cherry-pick this PR to all maintained release branches. Example PR: https://github.com/stackitcloud/cloud-provider-stackit/pull/756
56
58
5. Create a manual release for the new branch (note: the release tool will only work if there is already a tag on the branch). Do not generate release notes as they will contain many unrelated changes. Just add `Initial release of v1.xx.0` as release notes.
59
+
6. Add the new version in the `README.md`.
60
+
61
+
## Remove an Old Kubernetes Version
62
+
63
+
If a Kubernetes version is EOL and it is not possible to create SKE clusters with that version, the support for Kubernetes version can be removed.
64
+
65
+
1. Release the version a last time (if there are changes).
66
+
2. Remove the release branch in `.github/renovate.json5` under `baseBranchPatterns`.
67
+
3. Remove the `packageRules` for the release branch in `.github/renovate.json5`.
0 commit comments