DirectorySecurity AdvisoriesPricing
Sign in
Directory
local-static-provisioner logoHELM

local-static-provisioner

Helm chart
Last changed
Request a free trial

Contact our team to test out this Helm chart and related images for free. Please also indicate any other images you would like to evaluate.

Overview
Chart tags
Default values
Chart metadata
Images

Tag:
Compare:

1
# Override the default chartname or releasename
2
nameOverride: ""
3
fullnameOverride: ""
4
rbac:
5
# rbac.create: `true` if rbac resources should be created
6
create: true
7
# list of additional rbac rules that may be needed by init containers
8
extraRules: []
9
# Defines whether to generate a serviceAccount
10
serviceAccount:
11
# serviceAccount.create: Whether to create a service account or not
12
create: true
13
# serviceAccount.name: The name of the service account to create or use
14
name: ""
15
# Indicates if PVs should be dependents of the owner Node.
16
setPVOwnerRef: false
17
# Provisioner clean volumes in process by default. If set to true, provisioner
18
# will use Jobs to clean.
19
useJobForCleaning: false
20
# Provisioner name contains Node.UID by default. If set to true, the provisioner
21
# name will only use Node.Name.
22
useNodeNameOnly: false
23
# Resync period in reflectors will be random between minResyncPeriod and
24
# 2*minResyncPeriod. Default: 5m0s.
25
#minResyncPeriod: 5m0s
26
27
# Additional volumes to create, for the default container and init containers
28
# to consume
29
additionalVolumes: []
30
# Mount the host's `/dev/` by default so that block device symlinks can be
31
# resolved by the containers
32
mountDevVolume: true
33
# Additional volumes to mount to the default container, the volumes should
34
# either be host paths or defined by additionalVolumes
35
additionalVolumeMounts: []
36
# Map of label key-value pairs to apply to the PVs created by the
37
# provisioner. Uncomment to add labels to the list.
38
#labelsForPV:
39
# pv-labels: can-be-selected
40
41
# Indicates if Windows DaemonSet should be created
42
enableWindows: false
43
# Configuration for classes of static volumes.
44
classes:
45
- name: fast-disks # Defines name of storage classes.
46
# Path on the host where local volumes of this storage class are mounted
47
# under.
48
hostDir: /mnt/fast-disks
49
# Optionally specify mount path of local volumes. By default, we use same
50
# path as hostDir in container.
51
# mountDir: /mnt/fast-disks
52
# The volume mode of created PersistentVolume object. Default to Filesystem
53
# if not specified.
54
volumeMode: Filesystem
55
# Access mode of the volume. default to ReadWriteOnce if not specified.
56
accessMode: ReadWriteOnce
57
# Filesystem type to mount.
58
# It applies only when the source path is a block device,
59
# and desire volume mode is Filesystem.
60
# Must be a filesystem type supported by the host operating system.
61
fsType: ext4
62
# File name pattern to discover. By default, discover all file names.
63
namePattern: "*"
64
# Restrict topology of provisioned volumes to specific labels
65
allowedTopologies:
66
blockCleanerCommand:
67
# Do a quick reset of the block device during its cleanup.
68
# - "/scripts/quick_reset.sh"
69
# or use dd to zero out block dev in two iterations by uncommenting these lines
70
# - "/scripts/dd_zero.sh"
71
# - "2"
72
# or run shred utility for 2 iteration.s
73
- "/scripts/shred.sh"
74
- "2"
75
# or blkdiscard utility by uncommenting the line below.
76
# - "/scripts/blkdiscard.sh"
77
# Uncomment to create storage class object with default configuration.
78
# storageClass: true
79
# Uncomment to create storage class object and configure it.
80
# storageClass:
81
# reclaimPolicy: Delete # Available reclaim policies: Delete/Retain, defaults: Delete.
82
# isDefaultClass: true # set as default class
83
# If you are using cluster autoscaler to scale the workload using volume provisioned by this storage class,
84
# set the provisioner of the storage class to another value other than the default.
85
# Ref: https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner/issues/288
86
# provisioner: kubernetes.io/no-provisioner
87
# Defines annotations for each Pod in the DaemonSet.
88
podAnnotations: {}
89
# Defines labels for each Pod in the DaemonSet.
90
podLabels: {}
91
# Defines Provisioner's image name including container registry.
92
image: cgr.dev/chainguard-private/local-volume-provisioner:2.10.0-r4@sha256:829f40e99d285f04b5ea81ca48cddab3cf1d02b78b9e4e2bccce261c3e18e5c9
93
# Defines Image download policy, see kubernetes documentation for available values.
94
# imagePullPolicy: Always
95
96
# Defines Image pull secrets for the provisioner image.
97
imagePullSecrets: []
98
# Additional command-line arguments to pass to the provisioner container, in
99
# both the Linux and Windows DaemonSets.
100
#
101
# Example:
102
# additionalArgs:
103
# - --stderrthreshold=INFO
104
# - --v=2
105
additionalArgs: []
106
# Defines a name of the Pod Priority Class to use with the Provisioner DaemonSet
107
# Note that if you want to make it critical, specify "system-cluster-critical"
108
# or "system-node-critical" and deploy in kube-system namespace.
109
# Ref: https://k8s.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/#marking-pod-as-critical
110
#priorityClassName: system-node-critical
111
# If configured, nodeSelector will add a nodeSelector field to the DaemonSet PodSpec.
112
#
113
# NodeSelector constraint for local-volume-provisioner scheduling to nodes.
114
# Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#nodeselector
115
nodeSelector: {}
116
nodeSelectorWindows: {}
117
# List of node labels to be copied to the PVs created by the provisioner in a format:
118
#
119
# nodeLabels:
120
# - failure-domain.beta.kubernetes.io/zone
121
# - failure-domain.beta.kubernetes.io/region
122
#
123
# If configured, tolerations will add a toleration field to the DaemonSet PodSpec.
124
#
125
# Node tolerations for local-volume-provisioner scheduling to nodes with taints.
126
# Ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
127
tolerations: []
128
#
129
# If configured, removeNodeNotReadyTaint will add provisionerNotReadyNodeTaintKey as the toleration key
130
# to the DaemonSet PodSpec.
131
#
132
# removeNodeNotReadyTaint controls whether the provisioner should remove the provisionerNotReadyNodeTaintKey
133
# once it becomes ready.
134
removeNodeNotReadyTaint: false
135
#
136
# The key of the startup taint that provisioner will remove once it becomes ready.
137
# Ref: https://karpenter.sh/docs/concepts/nodepools/#cilium-startup-taint
138
provisionerNotReadyNodeTaintKey: "sig-storage-local-static-provisioner/agent-not-ready"
139
#
140
# If configured, affinity will add a affinity filed to the DeamonSet PodSpec.
141
# Ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity
142
affinity: {}
143
#
144
# If configured, resources will set the requests/limits field to the Daemonset PodSpec.
145
# Ref: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
146
resources: {}
147
# limits:
148
# memory: "512Mi"
149
# cpu: "1000m"
150
# requests:
151
# memory: "32Mi"
152
# cpu: "10m"
153
#
154
# Security context for the Linux provisioner container.
155
# This applies only to the Linux DaemonSet; the Windows DaemonSet does not
156
# render a securityContext.
157
# When set to a non-empty map/object value, this takes precedence over the legacy
158
# `privileged` field below. However, if `securityContext` does not include
159
# the `privileged` key, the legacy `privileged` value is automatically merged
160
# to preserve backward compatibility.
161
# Ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
162
#
163
# Example:
164
# securityContext:
165
# privileged: true
166
# allowPrivilegeEscalation: true
167
securityContext: {}
168
# If set to false, the provisioner DaemonSet container will run without extra
169
# privileges. This is the legacy field; when securityContext above is a non-empty
170
# map/object and includes the `privileged` key, this field is ignored.
171
privileged: true
172
# Host PID set in the linux daemonset container spec. When set to true allows a pod to have access to the host process ID namespace
173
hostPID: false
174
# Liveness probe for the provisioner container.
175
# Uses tcpSocket to verify the process is alive without coupling to readiness state.
176
# Ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
177
livenessProbe:
178
tcpSocket:
179
port: metrics
180
initialDelaySeconds: 10
181
periodSeconds: 60
182
timeoutSeconds: 5
183
failureThreshold: 3
184
# Readiness probe for the provisioner container.
185
readinessProbe: {}
186
# Startup probe for the provisioner container.
187
startupProbe: {}
188
# Any init containers can be configured here.
189
# Ref: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/
190
initContainers: []
191
# Update strategy for the DaemonSet.
192
updateStrategy:
193
type: RollingUpdate
194
rollingUpdate:
195
maxUnavailable: 1
196
#
197
# Configure Prometheus monitoring
198
#
199
serviceMonitor:
200
enabled: false
201
## Interval at which Prometheus scrapes the provisioner
202
interval: 10s
203
# Namespace Prometheus is installed in defaults to release namespace
204
namespace:
205
## Defaults to whats used if you follow CoreOS [Prometheus Install Instructions](https://github.com/coreos/prometheus-operator/tree/master/helm#tldr)
206
## [Prometheus Selector Label](https://github.com/coreos/prometheus-operator/blob/master/helm/prometheus/templates/prometheus.yaml#L65)
207
## [Kube Prometheus Selector Label](https://github.com/coreos/prometheus-operator/blob/master/helm/kube-prometheus/values.yaml#L298)
208
additionalLabels: {}
209
relabelings: []
210
# - sourceLabels: [__meta_kubernetes_pod_node_name]
211
# separator: ;
212
# regex: ^(.*)$
213
# targetLabel: nodename
214
# replacement: $1
215
# action: replace
216

The trusted source for open source

Talk to an expert
PrivacyTerms

Product

Chainguard ContainersChainguard LibrariesChainguard VMsChainguard OS PackagesChainguard ActionsChainguard Agent SkillsIntegrationsPricing
© 2026 Chainguard, Inc. All Rights Reserved.
Chainguard® and the Chainguard logo are registered trademarks of Chainguard, Inc. in the United States and/or other countries.
The other respective trademarks mentioned on this page are owned by the respective companies and use of them does not imply any affiliation or endorsement.