Merge pull request #857 from vdhanan/pdb

add pod disruption budget for csi controller

Author: k8s-ci-robot

Makefile

@@ -159,3 +159,4 @@ generate-kustomize: bin/helm
 	cd charts/aws-ebs-csi-driver && ../../bin/helm template kustomize . -s templates/serviceaccount-snapshot-controller.yaml -f ../../deploy/kubernetes/values/snapshotter.yaml > ../../deploy/kubernetes/overlays/alpha/serviceaccount-snapshot-controller.yaml
 	cd charts/aws-ebs-csi-driver && ../../bin/helm template kustomize . -s templates/snapshot-controller.yaml -f ../../deploy/kubernetes/values/snapshotter.yaml > ../../deploy/kubernetes/overlays/alpha/snapshot_controller.yaml
 	cd charts/aws-ebs-csi-driver && ../../bin/helm template kustomize . -s templates/serviceaccount-csi-node.yaml > ../../deploy/kubernetes/base/serviceaccount-csi-node.yaml
+	cd charts/aws-ebs-csi-driver && ../../bin/helm template kustomize . -s templates/controller-poddisruptionbudget.yaml > ../../deploy/kubernetes/base/controller-poddisruptionbudget.yaml

charts/aws-ebs-csi-driver/Chart.yaml

@@ -2,7 +2,7 @@ apiVersion: v1
 appVersion: "0.10.1"
 name: aws-ebs-csi-driver
 description: A Helm chart for AWS EBS CSI Driver
-version: 0.10.2
+version: 0.10.3
 kubeVersion: ">=1.17.0-0"
 home: https://github.com/kubernetes-sigs/aws-ebs-csi-driver
 sources:

charts/aws-ebs-csi-driver/templates/controller-poddisruptionbudget.yaml

@@ -0,0 +1,11 @@
+---
+kind: PodDisruptionBudget
+apiVersion: policy/v1beta1
+metadata:
+  name: ebs-csi-controller-pod-disruption-budget
+  namespace: kube-system
+spec:
+  minAvailable: 1
+  selector:
+    matchLabels:
+      app: ebs-csi-controller

charts/aws-ebs-csi-driver/values.yaml

@@ -61,6 +61,8 @@ resources:
   # choice for the user. This also increases chances charts run on environments with little
   # resources, such as Minikube. If you do want to specify resources, uncomment the following
   # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
+  # Note that you will need to set resource requests if you want the cluster autoscaler to
+  # scale your nodes when you increase/decrease the number of ebs-csi-controller replicas.
   # limits:
   #   cpu: 100m
   #   memory: 128Mi

deploy/kubernetes/base/controller-poddisruptionbudget.yaml

@@ -0,0 +1,12 @@
+---
+# Source: aws-ebs-csi-driver/templates/controller-poddisruptionbudget.yaml
+kind: PodDisruptionBudget
+apiVersion: policy/v1beta1
+metadata:
+  name: ebs-csi-controller-pod-disruption-budget
+  namespace: kube-system
+spec:
+  minAvailable: 1
+  selector:
+    matchLabels:
+      app: ebs-csi-controller

deploy/kubernetes/base/controller.yaml

@@ -77,7 +77,7 @@ spec:
             periodSeconds: 10
             failureThreshold: 5
         - name: csi-provisioner
-          image: k8s.gcr.io/sig-storage/csi-provisioner:v2.0.2
+          image: k8s.gcr.io/sig-storage/csi-provisioner:v2.1.1
           args:
             - --csi-address=$(ADDRESS)
             - --v=5
@@ -91,7 +91,7 @@ spec:
             - name: socket-dir
               mountPath: /var/lib/csi/sockets/pluginproxy/
         - name: csi-attacher
-          image: k8s.gcr.io/sig-storage/csi-attacher:v3.0.0
+          image: k8s.gcr.io/sig-storage/csi-attacher:v3.1.0
           args:
             - --csi-address=$(ADDRESS)
             - --v=5

deploy/kubernetes/base/kustomization.yaml

@@ -7,6 +7,7 @@ resources:
 - clusterrolebinding-attacher.yaml
 - clusterrolebinding-provisioner.yaml
 - controller.yaml
+- controller-poddisruptionbudget.yaml
 - csidriver.yaml
 - node.yaml
 - serviceaccount-csi-controller.yaml

deploy/kubernetes/base/node.yaml

@@ -72,7 +72,7 @@ spec:
             periodSeconds: 10
             failureThreshold: 5
         - name: node-driver-registrar
-          image: k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.0.1
+          image: k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.1.0
           args:
             - --csi-address=$(ADDRESS)
             - --kubelet-registration-path=$(DRIVER_REG_SOCK_PATH)