mirror of
https://github.com/helm/charts.git
synced 2026-08-23 22:37:45 +00:00
19576 Improved Jenkins persistence parameters documentation (#19577)
* 19576 Improved Jenkins persistence parameters documentation Signed-off-by: Fabio Kruger <krufab@gmail.com> * 19576 Updated CHANGELOG.md Signed-off-by: Fabio Kruger <krufab@gmail.com>
This commit is contained in:
committed by
Kubernetes Prow Robot
parent
7a6df7ac37
commit
f13d9649ab
@@ -5,6 +5,10 @@ numbering uses [semantic versioning](http://semver.org).
|
||||
|
||||
NOTE: The change log until version 1.5.7 is auto generated based on git commits. Those include a reference to the git commit to be able to get more details.
|
||||
|
||||
## 1.9.10
|
||||
|
||||
Added documentation for `persistence.storageClass`.
|
||||
|
||||
## 1.9.9
|
||||
Make `master.deploymentAnnotation` configurable.
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
apiVersion: v1
|
||||
name: jenkins
|
||||
home: https://jenkins.io/
|
||||
version: 1.9.9
|
||||
version: 1.9.10
|
||||
appVersion: lts
|
||||
description: Open source continuous integration server. It supports multiple SCM tools
|
||||
including CVS, Subversion and Git. It can execute Apache Ant and Apache Maven-based
|
||||
|
||||
@@ -303,6 +303,7 @@ It is possible to mount several volumes using `persistence.volumes` and `persist
|
||||
| --------------------------- | ------------------------------- | --------------- |
|
||||
| `persistence.enabled` | Enable the use of a Jenkins PVC | `true` |
|
||||
| `persistence.existingClaim` | Provide the name of a PVC | `nil` |
|
||||
| `persistence.storageClass` | Storage class for the PVC | `nil` |
|
||||
| `persistence.annotations` | Annotations for the PVC | `{}` |
|
||||
| `persistence.accessMode` | The PVC access mode | `ReadWriteOnce` |
|
||||
| `persistence.size` | The size of the PVC | `8Gi` |
|
||||
@@ -320,6 +321,19 @@ It is possible to mount several volumes using `persistence.volumes` and `persist
|
||||
$ helm install --name my-release --set persistence.existingClaim=PVC_NAME stable/jenkins
|
||||
```
|
||||
|
||||
#### Storage Class
|
||||
|
||||
It is possible to define which storage class to use:
|
||||
|
||||
```bash
|
||||
$ helm install --name my-release --set persistence.storageClass=customStorageClass stable/jenkins
|
||||
```
|
||||
|
||||
If set to a dash (`-`, as in `persistence.storageClass=-`), the dynamic provision is disabled.
|
||||
|
||||
If the storage class is set to null or left undefined (`persistence.storageClass=`),
|
||||
the default provisioner is used (gp2 on AWS, standard on GKE, AWS & OpenStack).
|
||||
|
||||
## Configuration as Code
|
||||
Jenkins Configuration as Code is now a standard component in the Jenkins project. Add a key under configScripts for each configuration area, where each corresponds to a plugin or section of the UI. The keys (prior to | character) are just labels, and can be any value. They are only used to give the section a meaningful name. The only restriction is they must conform to RFC 1123 definition of a DNS label, so may only contain lowercase letters, numbers, and hyphens. Each key will become the name of a configuration yaml file on the master in /var/jenkins_home/casc_configs (by default) and will be processed by the Configuration as Code Plugin during Jenkins startup. The lines after each | become the content of the configuration yaml file. The first line after this is a JCasC root element, eg jenkins, credentials, etc. Best reference is the Documentation link here: https://<jenkins_url>/configuration-as-code. The example below creates ldap settings:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user