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
Copy file name to clipboardExpand all lines: charts/jenkins/Chart.yaml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
apiVersion: v2
2
2
name: jenkins
3
3
home: https://jenkins.io/
4
-
version: 3.0.14
4
+
version: 3.1.0
5
5
appVersion: 2.263.1
6
6
description: Jenkins - Build great things at any scale! The leading open source automation server, Jenkins provides hundreds of plugins to support building, deploying and automating any project.
Copy file name to clipboardExpand all lines: charts/jenkins/README.md
+32-2Lines changed: 32 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -292,8 +292,38 @@ See additional `persistence` values using [configuration commands](#configuratio
292
292
#### Existing PersistentVolumeClaim
293
293
294
294
1. Create the PersistentVolume
295
-
1. Create the PersistentVolumeClaim
296
-
1. [Install](#install-chart) the chart, setting `persistence.existingClaim` to `PVC_NAME`
295
+
2. Create the PersistentVolumeClaim
296
+
3. [Install](#install-chart) the chart, setting `persistence.existingClaim` to `PVC_NAME`
297
+
298
+
#### Long Volume Attach/Mount Times
299
+
300
+
Certain volume type and filesystem format combinations may experience long
301
+
attach/mount times, [10 or more minutes][K8S_VOLUME_TIMEOUT], when using
302
+
`fsGroup`. This issue may result in the following entries in the pod's event
303
+
history:
304
+
305
+
```console
306
+
Warning FailedMount 38m kubelet, aks-default-41587790-2 Unable to attach or mount volumes: unmounted volumes=[jenkins-home], unattached volumes=[plugins plugin-dir jenkins-token-rmq2g sc-config-volume tmp jenkins-home jenkins-config secrets-dir]: timed out waiting for the condition
307
+
```
308
+
309
+
In these cases, experiment with replacing `fsGroup` with
310
+
`supplementalGroups`in the pod's `securityContext`. This can be achieved by
311
+
setting the `controller.podSecurityContextOverride` Helm chart value to
312
+
something like:
313
+
314
+
```yaml
315
+
controller:
316
+
podSecurityContextOverride:
317
+
runAsNonRoot: true
318
+
runAsUser: 1000
319
+
supplementalGroups: [1000]
320
+
```
321
+
322
+
This issue has been reported on [azureDisk with ext4][K8S_VOLUME_TIMEOUT] and
|`controller.initContainerEnv`| Environment variables for Init Container | Not set |
101
101
|`controller.containerEnv`| Environment variables for Jenkins Container | Not set |
102
-
|`controller.usePodSecurityContext`| Enable pod security context (must be `true` if `runAsUser` or `fsGroup` are set) |`true`|
103
-
|`controller.runAsUser`| uid that jenkins runs with |`1000`|
104
-
|`controller.fsGroup`| uid that will be used for persistent volume |`1000`|
102
+
|`controller.usePodSecurityContext`| Enable pod security context (must be `true` if `runAsUser`, `fsGroup`, or `podSecurityContextOverride` are set) |`true`|
103
+
|`controller.runAsUser`| Deprecated in favor of `controller.podSecurityContextOverride`. uid that jenkins runs with. |`1000`|
104
+
|`controller.fsGroup`| Deprecated in favor of `controller.podSecurityContextOverride`. uid that will be used for persistent volume. |`1000`|
105
+
|`controller.podSecurityContextOverride`| Completely overwrites the contents of the pod security context, ignoring the values provided for `runAsUser`, and `fsGroup`. | Not set |
105
106
|`controller.hostAliases`| Aliases for IPs in `/etc/hosts`|`[]`|
106
107
|`controller.serviceAnnotations`| Service annotations |`{}`|
107
108
|`controller.serviceType`| k8s service type |`ClusterIP`|
@@ -337,3 +338,7 @@ The following tables list the configurable parameters of the Jenkins chart and t
|`backup.destination`| Destination to store backup artifacts |`s3://jenkins-data/backup`|
339
340
|`backup.onlyJobs`| Only backup the job folder |`false`|
341
+
|`backup.usePodSecurityContext`| Enable backup pod's security context (must be `true` if `runAsUser`, `fsGroup`, or `podSecurityContextOverride` are set) |`true`|
342
+
|`backup.runAsUser`| Deprecated in favor of `backup.podSecurityContextOverride`. uid that jenkins runs with. |`1000`|
343
+
|`backup.fsGroup`| Deprecated in favor of `backup.podSecurityContextOverride`. uid that will be used for persistent volume. |`1000`|
344
+
|`backup.podSecurityContextOverride`| Completely overwrites the contents of the backup pod's security context, ignoring the values provided for `runAsUser`, and `fsGroup`. | Not set |
{{/* The rest of this section should be replaced with the contents of this comment one the runAsUser, fsGroup, and securityContextCapabilities Helm chart values have been removed:
0 commit comments