Backport the k8s 1.9 required action release note

kubernetes · Jan 19, 2020 · cf5cb6f · cf5cb6f
1 parent b926413
commit cf5cb6f
Show file tree

Hide file tree

Showing 3 changed files with 36 additions and 0 deletions.
diff --git a/docs/releases/1.15-NOTES.md b/docs/releases/1.15-NOTES.md
@@ -35,6 +35,18 @@ is safer.
   apiGroup will now be kops.k8s.io, not kops.  If performing strict string
   comparison you will need to update your expected values.
 
+* Kubernetes 1.9 users will need to enable the PodPriority feature gate. This is required for newer versions of Kops.
+
+  To enable the Pod priority feature, follow these steps:
+  ```
+  kops edit cluster
+  # Add the following section
+  spec:
+    kubelet:
+      featureGates:
+        PodPriority: "true"
+  ```
+
 # Full change list since 1.14.0 release
 
 ## kops 1.14.0-beta.2 to 1.15.0-alpha.1

diff --git a/docs/releases/1.16-NOTES.md b/docs/releases/1.16-NOTES.md
@@ -27,6 +27,18 @@ the notes prior to the release).
   a kops-controller Deployment may have been created that should get deleted.
   Run `kubectl -n kube-system delete deployment kops-controller` after upgrading to Kops 1.16.0-beta.1 or later.
 
+* Kubernetes 1.9 users will need to enable the PodPriority feature gate. This is required for newer versions of Kops.
+
+  To enable the Pod priority feature, follow these steps:
+  ```
+  kops edit cluster
+  # Add the following section
+  spec:
+    kubelet:
+      featureGates:
+        PodPriority: "true"
+  ```
+
 # Full change list since 1.15.0 release
 
 ## 1.15.0-alpha.1 to 1.16.0-alpha.1

diff --git a/docs/releases/1.17-NOTES.md b/docs/releases/1.17-NOTES.md
@@ -39,6 +39,18 @@ the notes prior to the release).
   terraform apply
   ```
 
+* Kubernetes 1.9 users will need to enable the PodPriority feature gate. This is required for newer versions of Kops.
+
+  To enable the Pod priority feature, follow these steps:
+  ```
+  kops edit cluster
+  # Add the following section
+  spec:
+    kubelet:
+      featureGates:
+        PodPriority: "true"
+  ```
+
 * If either a Kops 1.17 alpha release or a custom Kops build was used on a cluster,
   a kops-controller Deployment may have been created that should get deleted because it has been replaced with a DaemonSet.
   Run `kubectl -n kube-system delete deployment kops-controller` after upgrading to Kops 1.17.0-alpha.2 or later.