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: docs/howto/upgrade-cluster/index.md
+20-13Lines changed: 20 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -11,19 +11,26 @@ clusters on AWS.
11
11
12
12
## Upgrade policy
13
13
14
-
We aim to ensure we use a k8s version for the control plane and node groups that is at least **five minor versions** behind the latest one available at any given time.
15
-
16
-
Ideally, the following rules should also be respected:
17
-
18
-
1. Every new cluster we deploy should be using the latest available kubernetes version.
19
-
1. All of the clusters deployed in a cloud provider should be using the same version.
20
-
1. Check if new upgrades are needed at least every 3 months.
21
-
22
-
23
-
```{warning}
24
-
As of now, we have not yet established practices on how to ensure these upgrades happen according to the policy above. Establishing this is tracked in [this GitHub
0 commit comments