# This YAML file shows how to deploy the snapshot controller # The snapshot controller implements the control loop for CSI snapshot functionality. # It should be installed as part of the base Kubernetes distribution in an appropriate # namespace for components implementing base system functionality. For installing with # Vanilla Kubernetes, kube-system makes sense for the namespace. --- kind: Deployment apiVersion: apps/v1 metadata: name: snapshot-controller namespace: kube-system spec: replicas: 2 selector: matchLabels: app: snapshot-controller # the snapshot controller won't be marked as ready if the v1 CRDs are unavailable # in #504 the snapshot-controller will exit after around 7.5 seconds if it # can't find the v1 CRDs so this value should be greater than that minReadySeconds: 15 strategy: rollingUpdate: maxSurge: 0 maxUnavailable: 1 type: RollingUpdate template: metadata: labels: app: snapshot-controller spec: serviceAccountName: snapshot-controller nodeSelector: kubernetes.io/os: linux priorityClassName: system-cluster-critical securityContext: seccompProfile: type: RuntimeDefault tolerations: - key: "node-role.kubernetes.io/master" operator: "Equal" value: "true" effect: "NoSchedule" - key: "node-role.kubernetes.io/controlplane" operator: "Equal" value: "true" effect: "NoSchedule" - key: "node-role.kubernetes.io/control-plane" operator: "Equal" value: "true" effect: "NoSchedule" containers: - name: snapshot-controller image: registry.k8s.io/sig-storage/snapshot-controller:v6.3.3 args: - "--v=2" - "--leader-election=true" - "--leader-election-namespace=kube-system" resources: limits: memory: 300Mi requests: cpu: 10m memory: 20Mi securityContext: capabilities: drop: - ALL