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
| args | list |`["--v=5","--leader-election=true","--http-endpoint=:8080"]`| Possible arguments can be found in the [Snapshot Controller command-line options](https://github.com/kubernetes-csi/external-snapshotter#snapshot-controller-command-line-options)|
19
+
| autoscaling.enabled | bool |`false`||
20
+
| autoscaling.maxReplicas | int |`100`| HPA Max Replicas |
21
+
| autoscaling.minReplicas | int |`1`||
22
+
| autoscaling.targetCPUUtilizationPercentage | int |`80`||
23
+
| fullnameOverride | string |`""`| Full name override |
24
+
| image.pullPolicy | string |`"IfNotPresent"`| Image pull policy strategy when the kubelet attempts to pull(download) the specified image |
25
+
| image.repository | string |`"gcr.io/k8s-staging-sig-storage/snapshot-controller"`| Image to use for deploying |
26
+
| image.tag | string |`"v5.0.0-rc1"`| Overrides the image tag whose default is the chart appVersion. |
27
+
| imagePullSecrets | list |`[]`| Add image pull secrets if requires |
28
+
| minReadySeconds | int |`15`| The snapshot controller won't be marked as ready if the v1 CRDs are unavailable in [#504](https://github.com/kubernetes-csi/external-snapshotter/pull/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 |
| rollingUpdate.maxSurge | int |`0`| Max number of pods that can be created above the desired number of replicas |
39
+
| securityContext | object |`{}`||
40
+
| service.port | int |`8080`||
41
+
| service.type | string |`"ClusterIP"`||
42
+
| serviceAccount.annotations | object |`{}`| Annotations to add to the service account |
43
+
| serviceAccount.create | bool |`true`| Specifies whether a service account should be created |
44
+
| serviceAccount.name | string |`""`| The name of the service account to use. If not set and create is true, a name is generated using the fullname template |
45
+
| tolerations | list |`[]`| Allow the pods to schedule onto nodes with matching taints |
46
+
47
+
----------------------------------------------
48
+
Autogenerated from chart metadata using [helm-docs v1.5.0](https://github.com/norwoodj/helm-docs/releases/v1.5.0)
To verify that snapshot-controller has started, run:
4
+
5
+
kubectl get pod -n {{ .Release.Namespace }} -l "app.kubernetes.io/name={{ include "snapshot-controller.name" . }},app.kubernetes.io/instance={{ .Release.Name }}"
0 commit comments