home/charts
2
0
Fork 0
mirror of https://github.com/wahyd4/charts.git synced 2026-08-21 11:06:10 +10:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'master' into master

Browse Source
This commit is contained in:
Carlos Rodríguez Hernández
2019-05-30 09:12:47 +02:00
committed by GitHub
parent 774b390424 b1f0a6e3ec
commit 062ff0a464
270 changed files with 3397 additions and 608 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+1
View File
@@ -59,6 +59,7 @@ $ helm search bitnami
- [nginx](https://github.com/bitnami/charts/tree/master/bitnami/nginx)
- [nginx-ingress-controller](https://github.com/bitnami/charts/tree/master/bitnami/nginx-ingress-controller)
- [NodeJS](https://github.com/bitnami/charts/tree/master/bitnami/node)
- [PyTorch](https://github.com/bitnami/charts/tree/master/bitnami/pytorch)
- [TensorFlow ResNet](https://github.com/bitnami/charts/tree/master/bitnami/tensorflow-resnet)
- [Tomcat](https://github.com/bitnami/charts/tree/master/bitnami/tomcat)
- [WildFly](https://github.com/bitnami/charts/tree/master/bitnami/wildfly)
bitnami/airflow/Chart.yaml
+1 -1
View File
@@ -1,6 +1,6 @@
apiVersion: v1
name: airflow
version: 0.0.4
version: 0.1.2
appVersion: 1.10.3
description: Apache Airflow is a platform to programmatically author, schedule and monitor workflows.
keywords:
bitnami/airflow/README.md
+16 -9
View File
@@ -51,25 +51,25 @@ The following tables lists the configurable parameters of the Kafka chart and th
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.registry` | Airflow image registry | `docker.io` |
| `image.repository` | Airflow image name | `bitnami/airflow` |
| `image.tag` | Airflow image tag | `{VERSION}` |
| `image.tag` | Airflow image tag | `{TAG_NAME}` |
| `image.pullPolicy` | Airflow image pull policy | `Always` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.debug` | Specify if debug values should be set | `false` |
| `schedulerImage.registry` | Airflow Scheduler image registry | `docker.io` |
| `schedulerImage.repository` | Airflow Scheduler image name | `bitnami/airflow-shceduler` |
| `schedulerImage.tag` | Airflow Scheduler image tag | `{VERSION}` |
| `schedulerImage.tag` | Airflow Scheduler image tag | `{TAG_NAME}` |
| `schedulerImage.pullPolicy` | Airflow Scheduler image pull policy | `Always` |
| `schedulerImage.pullSecrets` | Specify docker-registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `schedulerImage.debug` | Specify if debug values should be set | `false` |
| `workerImage.registry` | Airflow Worker image registry | `docker.io` |
| `workerImage.repository` | Airflow Worker image name | `bitnami/airflow-worker` |
| `workerImage.tag` | Airflow Worker image tag | `{VERSION}` |
| `workerImage.tag` | Airflow Worker image tag | `{TAG_NAME}` |
| `workerImage.pullPolicy` | Airflow Worker image pull policy | `Always` |
| `workerImage.pullSecrets` | Specify docker-registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `workerImage.debug` | Specify if debug values should be set | `false` |
| `git.registry` | Git image registry | `docker.io` |
| `git.repository` | Git image name | `bitnami/git` |
| `git.tag` | Git image tag | `{VERSION}` |
| `git.tag` | Git image tag | `{TAG_NAME}` |
| `git.pullPolicy` | Git image pull policy | `Always` |
| `git.pullSecrets` | Specify docker-registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `updateStrategy` | Update strategy for the stateful set | `RollingUpdate` |
@@ -79,7 +79,8 @@ The following tables lists the configurable parameters of the Kafka chart and th
| `airflow.loadExamples` | Switch to load some Airflow examples | `true` |
| `airflow.cloneDagFilesFromGit.enabled` | Enable in order to download DAG files from git repository. | `false` |
| `airflow.cloneDagFilesFromGit.repository` | Repository where download DAG files from | `nil` |
| `airflow.cloneDagFilesFromGit.revision` | Revision from repository to checkout | `nil` |
| `airflow.cloneDagFilesFromGit.branch` | Branch from repository to checkout | `nil` |
| `airflow.cloneDagFilesFromGit.interval` | Interval to pull the repository on sidecar container | `nil` |
| `airflow.baseUrl` | URL used to access to airflow web ui | `nil` |
| `airflow.worker.port` | Airflow Worker port | `8793` |
| `airflow.worker.replicas` | Number of Airflow Worker replicas | `2` |
@@ -164,6 +165,12 @@ $ helm install --name my-release -f values.yaml bitnami/airflow
> **Tip**: You can use the default [values.yaml](values.yaml)
### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
## Persistence
The Bitnami Airflow chart relies on the PostgreSQL chart persistence. This means that Airflow does not persist anything.
@@ -188,12 +195,12 @@ You can manually create a config map containing all your DAG files and then pass
### Option 3: Get your DAG files from a git repository
You can store all your DAG files on a GitHub repository and then clone to the Airflow pods with an initContainer. In order to do that, you can deploy airflow with the following options:
You can store all your DAG files on a GitHub repository and then clone to the Airflow pods with an initContainer. The repository will be periodically updated using a sidecar container. In order to do that, you can deploy airflow with the following options:
```console
helm install --name my-release bitnami/airflow \
--set airflow.cloneDagFilesFromGit.enabled=true \
--set airflow.cloneDagFilesFromGit.repository=https://github.com/USERNAME/REPOSITORY \
--set airflow.cloneDagFilesFromGit.revision=master
```
--set airflow.cloneDagFilesFromGit.branch=master
--set airflow.cloneDagFilesFromGit.interval=60
```
bitnami/airflow/templates/NOTES.txt
+4 -1
View File
@@ -75,4 +75,7 @@ host. To configure Airflow with the URL of your service:
echo User: {{ .Values.airflow.auth.username }}
echo Password: $(kubectl get secret --namespace {{ .Release.Namespace }} {{ template "airflow.fullname" . }} -o jsonpath="{.data.airflow-password}" | base64 --decode)
{{- end }}
{{- end }}
{{ include "airflow.validateValues" . }}
{{ include "airflow.checkRollingTags" . }}
bitnami/airflow/templates/_helpers.tpl
+53 -2
View File
@@ -146,7 +146,6 @@ Also, we can't use a single if because lazy evaluation is not an option
{{- end -}}
{{- end -}}
{{/*
Return the proper Docker Image Registry Secret Names
*/}}
@@ -233,4 +232,56 @@ Get the secret name
{{- else -}}
{{- printf "%s" (include "airflow.fullname" .) -}}
{{- end -}}
{{- end -}}
{{- end -}}
{{/*
Compile all warnings into a single message, and call fail.
*/}}
{{- define "airflow.validateValues" -}}
{{- $messages := list -}}
{{- $messages := append $messages (include "airflow.validateValues.cloneDagFilesFromGit.repository" .) -}}
{{- $messages := append $messages (include "airflow.validateValues.cloneDagFilesFromGit.branch" .) -}}
{{- $messages := without $messages "" -}}
{{- $message := join "\n" $messages -}}
{{- if $message -}}
{{- printf "\nVALUES VALIDATION:\n%s" $message | fail -}}
{{- end -}}
{{- end -}}
{{/* Validate values of Airflow - "airflow.cloneDagFilesFromGit.repository" must be provided when "airflow.cloneDagFilesFromGit.enabled" is "true" */}}
{{- define "airflow.validateValues.cloneDagFilesFromGit.repository" -}}
{{- if and .Values.airflow.cloneDagFilesFromGit.enabled (empty .Values.airflow.cloneDagFilesFromGit.repository) -}}
airflow: airflow.cloneDagFilesFromGit.repository
The repository must be provided when enabling downloading DAG files
from git repository (--set airflow.cloneDagFilesFromGit.repository="xxx")
{{- end -}}
{{- end -}}
{{/* Validate values of Airflow - "airflow.cloneDagFilesFromGit.branch" must be provided when "airflow.cloneDagFilesFromGit.enabled" is "true" */}}
{{- define "airflow.validateValues.cloneDagFilesFromGit.branch" -}}
{{- if and .Values.airflow.cloneDagFilesFromGit.enabled (empty .Values.airflow.cloneDagFilesFromGit.branch) -}}
airflow: airflow.cloneDagFilesFromGit.branch
The branch must be provided when enabling downloading DAG files
from git repository (--set airflow.cloneDagFilesFromGit.branch="xxx")
{{- end -}}
{{- end -}}
{{/* Check if there are rolling tags in the images */}}
{{- define "airflow.checkRollingTags" -}}
{{- if and (contains "bitnami/" .Values.image.repository) (not (.Values.image.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.image.repository }}:{{ .Values.image.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
{{- if and (contains "bitnami/" .Values.schedulerImage.repository) (not (.Values.schedulerImage.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.schedulerImage.repository }}:{{ .Values.schedulerImage.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
{{- if and (contains "bitnami/" .Values.workerImage.repository) (not (.Values.workerImage.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.workerImage.repository }}:{{ .Values.workerImage.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
{{- if and (contains "bitnami/" .Values.git.repository) (not (.Values.git.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.git.repository }}:{{ .Values.git.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
{{- end -}}
bitnami/airflow/templates/deployment-scheduler.yaml
+23 -3
View File
@@ -50,12 +50,32 @@ spec:
- name: git-clone-repository
image: "{{ template "git.image" . }}"
imagePullPolicy: {{ .Values.git.pullPolicy | quote }}
command: [ '/bin/sh', '-c' , 'git clone {{ .Values.airflow.cloneDagFilesFromGit.repository }} /dags && cd /dags && git checkout {{ .Values.airflow.cloneDagFilesFromGit.revision }}']
command:
- /bin/bash
- -ec
- |
git clone {{ .Values.airflow.cloneDagFilesFromGit.repository }} --branch {{ .Values.airflow.cloneDagFilesFromGit.branch }} /dags
volumeMounts:
- name: git-cloned-dag-files
mountPath: /dags
{{- end }}
containers:
- name: git-repo-syncer
image: "{{ template "git.image" . }}"
imagePullPolicy: {{ .Values.git.pullPolicy | quote }}
command:
- /bin/bash
- -ec
- |
while true; do
cd /dags && git pull origin {{ .Values.airflow.cloneDagFilesFromGit.branch }}
sleep {{ default "60" .Values.airflow.cloneDagFilesFromGit.interval }}
done
volumeMounts:
- name: git-cloned-dag-files
mountPath: /dags
{{- else }}
containers:
{{- end }}
- name: airflow-scheduler
image: {{ template "airflow.schedulerImage" . }}
imagePullPolicy: {{ .Values.schedulerImage.pullPolicy | quote }}
@@ -187,4 +207,4 @@ spec:
- name: custom-configuration-file
configMap:
name: {{ .Values.airflow.configurationConfigMap }}
{{- end }}
{{- end }}
bitnami/airflow/templates/deployment-web.yaml
+23 -3
View File
@@ -50,12 +50,32 @@ spec:
- name: git-clone-repository
image: "{{ template "git.image" . }}"
imagePullPolicy: {{ .Values.git.pullPolicy | quote }}
command: [ '/bin/sh', '-c' , 'git clone {{ .Values.airflow.cloneDagFilesFromGit.repository }} /dags && cd /dags && git checkout {{ .Values.airflow.cloneDagFilesFromGit.revision }}']
command:
- /bin/bash
- -ec
- |
git clone {{ .Values.airflow.cloneDagFilesFromGit.repository }} --branch {{ .Values.airflow.cloneDagFilesFromGit.branch }} /dags
volumeMounts:
- name: git-cloned-dag-files
mountPath: /dags
{{- end }}
containers:
- name: git-repo-syncer
image: "{{ template "git.image" . }}"
imagePullPolicy: {{ .Values.git.pullPolicy | quote }}
command:
- /bin/bash
- -ec
- |
while true; do
cd /dags && git pull origin {{ .Values.airflow.cloneDagFilesFromGit.branch }}
sleep {{ default "60" .Values.airflow.cloneDagFilesFromGit.interval }}
done
volumeMounts:
- name: git-cloned-dag-files
mountPath: /dags
{{- else }}
containers:
{{- end }}
- name: airflow-web
image: {{ template "airflow.image" . }}
imagePullPolicy: {{ .Values.image.pullPolicy | quote }}
@@ -217,4 +237,4 @@ spec:
- name: custom-configuration-file
configMap:
name: {{ .Values.airflow.configurationConfigMap }}
{{- end }}
{{- end }}
bitnami/airflow/templates/statefulset-worker.yaml
+23 -3
View File
@@ -54,12 +54,32 @@ spec:
- name: git-clone-repository
image: "{{ template "git.image" . }}"
imagePullPolicy: {{ .Values.git.pullPolicy | quote }}
command: [ '/bin/sh', '-c' , 'git clone {{ .Values.airflow.cloneDagFilesFromGit.repository }} /dags && cd /dags && git checkout {{ .Values.airflow.cloneDagFilesFromGit.revision }}']
command:
- /bin/bash
- -ec
- |
git clone {{ .Values.airflow.cloneDagFilesFromGit.repository }} --branch {{ .Values.airflow.cloneDagFilesFromGit.branch }} /dags
volumeMounts:
- name: git-cloned-dag-files
mountPath: /dags
{{- end }}
containers:
- name: git-repo-syncer
image: "{{ template "git.image" . }}"
imagePullPolicy: {{ .Values.git.pullPolicy | quote }}
command:
- /bin/bash
- -ec
- |
while true; do
cd /dags && git pull origin {{ .Values.airflow.cloneDagFilesFromGit.branch }}
sleep {{ default "60" .Values.airflow.cloneDagFilesFromGit.interval }}
done
volumeMounts:
- name: git-cloned-dag-files
mountPath: /dags
{{- else }}
containers:
{{- end }}
- name: airflow-worker
image: "{{ template "airflow.workerImage" . }}"
imagePullPolicy: "{{ .Values.workerImage.pullPolicy }}"
@@ -202,4 +222,4 @@ spec:
- name: custom-configuration-file
configMap:
name: {{ .Values.airflow.configurationConfigMap }}
{{- end }}
{{- end }}
bitnami/airflow/values-production.yaml
+8 -7
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/airflow
tag: 1.10.3
tag: 1.10.3-debian-9-r16
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -37,7 +37,7 @@ image:
schedulerImage:
registry: docker.io
repository: bitnami/airflow-scheduler
tag: 1.10.3
tag: 1.10.3-debian-9-r26
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -61,7 +61,7 @@ schedulerImage:
workerImage:
registry: docker.io
repository: bitnami/airflow-worker
tag: 1.10.3
tag: 1.10.3-debian-9-r25
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -85,7 +85,7 @@ workerImage:
git:
registry: docker.io
repository: bitnami/git
tag: latest
tag: 2.21.0-debian-9-r72
pullPolicy: IfNotPresent
## Optionally specify an array of imagePullSecrets.
## Secrets must be manually created in the namespace.
@@ -120,8 +120,9 @@ airflow:
##
cloneDagFilesFromGit:
enabled: false
repository:
revision:
# repository:
# branch:
# interval:
## URL used to access to airflow web ui
##
baseUrl: http://airflow.local
@@ -354,4 +355,4 @@ metrics:
## Metrics exporter pod Annotation and Labels
# podAnnotations: {}
# podLabels: {}
# podLabels: {}
bitnami/airflow/values.yaml
+8 -7
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/airflow
tag: 1.10.3
tag: 1.10.3-debian-9-r16
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -37,7 +37,7 @@ image:
schedulerImage:
registry: docker.io
repository: bitnami/airflow-scheduler
tag: 1.10.3
tag: 1.10.3-debian-9-r26
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -61,7 +61,7 @@ schedulerImage:
workerImage:
registry: docker.io
repository: bitnami/airflow-worker
tag: 1.10.3
tag: 1.10.3-debian-9-r25
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -85,7 +85,7 @@ workerImage:
git:
registry: docker.io
repository: bitnami/git
tag: latest
tag: 2.21.0-debian-9-r72
pullPolicy: IfNotPresent
## Optionally specify an array of imagePullSecrets.
## Secrets must be manually created in the namespace.
@@ -119,9 +119,10 @@ airflow:
## Enable in order to download DAG files from git repository.
##
cloneDagFilesFromGit:
enabled: true
repository: https://github.com/tompizmor/sample-airflow-dag
revision: master
enabled: false
# repository:
# branch:
# interval:
## URL used to access to airflow web ui
##
# baseUrl:
bitnami/apache/Chart.yaml
+1 -1
View File
@@ -1,6 +1,6 @@
apiVersion: v1
name: apache
version: 4.2.0
version: 4.2.4
appVersion: 2.4.39
description: Chart for Apache HTTP Server
keywords:
bitnami/apache/README.md
+7 -1
View File
@@ -50,7 +50,7 @@ The following tables lists the configurable parameters of the Apache chart and t
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.registry` | Apache Docker image registry | `docker.io` |
| `image.repository` | Apache Docker image name | `bitnami/apache` |
| `image.tag` | Apache Docker image tag | `{VERSION}` |
| `image.tag` | Apache Docker image tag | `{TAG_NAME}` |
| `image.pullPolicy` | Apache Docker image pull policy | `Always` |
| `image.pullSecrets` | Specify Docker registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `podAnnotations` | Pod annotations | `{}` |
@@ -98,6 +98,12 @@ $ helm install --name my-release -f values.yaml bitnami/apache
> **Tip**: You can use the default [values.yaml](values.yaml)
### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
## Upgrading
### To 2.0.0
bitnami/apache/templates/NOTES.txt
+6
View File
@@ -0,0 +1,6 @@
{{- if and (contains "bitnami/" .Values.image.repository) (not (.Values.image.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.image.repository }}:{{ .Values.image.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
bitnami/apache/values.yaml
+1 -1
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/apache
tag: 2.4.39
tag: 2.4.39-debian-9-r31
## Specify a imagePullPolicy
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
##
bitnami/cassandra/Chart.yaml
+1 -1
View File
@@ -1,6 +1,6 @@
apiVersion: v1
name: cassandra
version: 2.3.3
version: 2.3.5
appVersion: 3.11.4
description: Apache Cassandra is a free and open-source distributed database management system designed to handle large amounts of data across many commodity servers, providing high availability with no single point of failure. Cassandra offers robust support for clusters spanning multiple datacenters, with asynchronous masterless replication allowing low latency operations for all clients.
icon: https://bitnami.com/assets/stacks/cassandra/img/cassandra-stack-220x234.png
bitnami/cassandra/README.md
+7 -1
View File
@@ -52,7 +52,7 @@ The following tables lists the configurable parameters of the cassandra chart an
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.registry` | Cassandra Image registry | `docker.io` |
| `image.repository` | Cassandra Image name | `bitnami/cassandra` |
| `image.tag` | Cassandra Image tag | `{VERSION}` |
| `image.tag` | Cassandra Image tag | `{TAG_NAME}` |
| `image.pullPolicy` | Image pull policy | `Always` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `service.type` | Kubernetes Service type | `ClusterIP` |
@@ -137,6 +137,12 @@ $ helm install --name my-release -f values.yaml bitnami/cassandra
> **Tip**: You can use the default [values.yaml](values.yaml)
### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
## Persistence
The [Bitnami cassandra](https://github.com/bitnami/bitnami-docker-cassandra) image stores the cassandra data at the `/bitnami/cassandra` path of the container.
bitnami/cassandra/templates/NOTES.txt
+7 -1
View File
@@ -38,7 +38,7 @@ To connect to your database from outside the cluster execute the following comma
export NODE_IP=$(kubectl get nodes --namespace {{ .Release.Namespace }} -o jsonpath="{.items[0].status.addresses[0].address}")
export NODE_PORT=$(kubectl get --namespace {{ .Release.Namespace }} -o jsonpath="{.spec.ports[0].nodePort}" services {{ template "cassandra.fullname" . }})
cqlsh -u {{ .Values.dbUser.user }} -p $CASSANDRA_PASSWORD $NODE_IP $NODE_PORT
{{- else if contains "LoadBalancer" .Values.service.type }}
@@ -57,3 +57,9 @@ To connect to your database from outside the cluster execute the following comma
{{- end }}
{{- end }}
{{- if and (contains "bitnami/" .Values.image.repository) (not (.Values.image.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.image.repository }}:{{ .Values.image.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
bitnami/cassandra/values-production.yaml
+1 -1
View File
@@ -16,7 +16,7 @@ image:
## Bitnami Cassandra image tag
## ref: https://github.com/bitnami/bitnami-docker-cassandra#supported-tags-and-respective-dockerfile-links
##
tag: 3.11.4
tag: 3.11.4-debian-9-r84
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
bitnami/cassandra/values.yaml
+1 -1
View File
@@ -16,7 +16,7 @@ image:
## Bitnami Cassandra image tag
## ref: https://github.com/bitnami/bitnami-docker-cassandra#supported-tags-and-respective-dockerfile-links
##
tag: 3.11.4
tag: 3.11.4-debian-9-r84
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
bitnami/consul/Chart.yaml
+2 -2
View File
@@ -1,7 +1,7 @@
apiVersion: v1
name: consul
version: 4.2.5
appVersion: 1.5.0
version: 4.2.8
appVersion: 1.5.1
description: Highly available and distributed service discovery and key-value store designed with support for the modern data center to make distributed systems and configuration easy.
home: https://www.consul.io/
sources:
bitnami/consul/README.md
+7 -1
View File
@@ -55,7 +55,7 @@ The following tables lists the configurable parameters of the HashiCorp Consul c
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.registry` | HashiCorp Consul image registry | `docker.io` |
| `image.repository` | HashiCorp Consul image name | `bitnami/consul` |
| `image.tag` | HashiCorp Consul image tag | `{VERSION}` |
| `image.tag` | HashiCorp Consul image tag | `{TAG_NAME}` |
| `image.pullPolicy` | Image pull policy | `Always` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `replicas` | Number of replicas | `3` |
@@ -133,6 +133,12 @@ $ helm install --name my-release -f values.yaml bitnami/consul
> **Tip**: You can use the default [values.yaml](values.yaml)
### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
## Persistence
The [Bitnami HashiCorp Consul](https://github.com/bitnami/bitnami-docker-consul) image stores the HashiCorp Consul data at the `/bitnami` path of the container.
bitnami/consul/templates/NOTES.txt
+7
View File
@@ -45,3 +45,10 @@ Furthermore, to know which Consul node is the cluster leader run this other comm
kubectl exec -it {{ template "consul.fullname" . }}-0 -- consul operator raft list-peers
{{- end }}
{{- if and (contains "bitnami/" .Values.image.repository) (not (.Values.image.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.image.repository }}:{{ .Values.image.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
bitnami/consul/values-production.yaml
+1 -1
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/consul
tag: 1.5.0
tag: 1.5.1-debian-9-r5
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
bitnami/consul/values.yaml
+1 -1
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/consul
tag: 1.5.0
tag: 1.5.1-debian-9-r5
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
bitnami/elasticsearch/Chart.yaml
+2 -2
View File
@@ -1,7 +1,7 @@
apiVersion: v1
name: elasticsearch
version: 5.0.1
appVersion: 7.0.1
version: 5.1.5
appVersion: 7.1.1
description: A highly scalable open-source full-text search and analytics engine
keywords:
- elasticsearch
bitnami/elasticsearch/README.md
+12 -1
View File
@@ -55,7 +55,7 @@ The following table lists the configurable parameters of the Elasticsearch chart
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.registry` | Elasticsearch image registry | `docker.io` |
| `image.repository` | Elasticsearch image repository | `bitnami/elasticsearch` |
| `image.tag` | Elasticsearch image tag | `{VERSION}` |
| `image.tag` | Elasticsearch image tag | `{TAG_NAME}` |
| `image.pullPolicy` | Image pull policy | `Always` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `name` | Elasticsearch cluster name | `elastic` |
@@ -78,6 +78,7 @@ The following table lists the configurable parameters of the Elasticsearch chart
| `master.livenessProbe.timeoutSeconds` | When the probe times out (master-eligible nodes pod) | `5` |
| `master.livenessProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed (master-eligible nodes pod) | `1` |
| `master.livenessProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded | `5` |
| `master.podAnnotations` | Annotations for master pods. | `{}` |
| `master.readinessProbe.enabled` | Enable/disable the readiness probe (master-eligible nodes pod) | `true` |
| `master.readinessProbe.initialDelaySeconds` | Delay before readiness probe is initiated (master-eligible nodes pod) | `90` |
| `master.readinessProbe.periodSeconds` | How often to perform the probe (master-eligible nodes pod) | `10` |
@@ -93,6 +94,7 @@ The following table lists the configurable parameters of the Elasticsearch chart
| `coordinating.heapSize` | Coordinating-only node heap size | `128m` |
| `coordinating.antiAffinity` | Coordinating-only node pod anti-affinity policy | `soft` |
| `coordinating.nodeAffinity` | Coordinating-only node affinity policy | `nil` |
| `coordinating.podAnnotations` | Annotations for coordniating pods. | `{}` |
| `coordinating.service.type` | Kubernetes Service type (coordinating-only nodes) | `ClusterIP` |
| `coordinating.service.port` | Kubernetes Service port for REST API (coordinating-only nodes) | `9200` |
| `coordinating.service.nodePort` | Kubernetes Service nodePort (coordinating-only nodes) | `nil` |
@@ -130,6 +132,7 @@ The following table lists the configurable parameters of the Elasticsearch chart
| `data.livenessProbe.timeoutSeconds` | When the probe times out (data nodes pod) | `5` |
| `data.livenessProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed (data nodes pod) | `1` |
| `data.livenessProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded | `5` |
| `data.podAnnotations` | Annotations for data pods. | `{}` |
| `data.readinessProbe.enabled` | Enable/disable the readiness probe (data nodes pod) | `true` |
| `data.readinessProbe.initialDelaySeconds` | Delay before readiness probe is initiated (data nodes pod) | `90` |
| `data.readinessProbe.periodSeconds` | How often to perform the probe (data nodes pod) | `10` |
@@ -154,6 +157,7 @@ The following table lists the configurable parameters of the Elasticsearch chart
| `ingest.livenessProbe.timeoutSeconds` | When the probe times out (ingest nodes pod) | `5` |
| `ingest.livenessProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed (ingest nodes pod) | `1` |
| `ingest.livenessProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded | `5` |
| `ingest.podAnnotations` | Annotations for ingest pods. | `{}` |
| `ingest.readinessProbe.enabled` | Enable/disable the readiness probe (ingest nodes pod) | `true` |
| `ingest.readinessProbe.initialDelaySeconds` | Delay before readiness probe is initiated (ingest nodes pod) | `90` |
| `ingest.readinessProbe.periodSeconds` | How often to perform the probe (ingest nodes pod) | `10` |
@@ -168,6 +172,7 @@ The following table lists the configurable parameters of the Elasticsearch chart
| `metrics.image.pullPolicy` | Metrics exporter image pull policy | `Always` |
| `metrics.service.type` | Metrics exporter endpoint service type | `ClusterIP` |
| `metrics.resources` | Metrics exporter resource requests/limit | `requests: { cpu: "25m" }` |
| `metrics.podAnnotations` | Annotations for metrics pods. | `{}` |
| `sysctlImage.enabled` | Enable kernel settings modifier image | `false` |
| `sysctlImage.registry` | Kernel settings modifier image registry | `docker.io` |
| `sysctlImage.repository` | Kernel settings modifier image repository | `bitnami/minideb` |
@@ -192,6 +197,12 @@ $ helm install --name my-release -f values.yaml bitnami/elasticsearch
> **Tip**: You can use the default [values.yaml](values.yaml). [values-production.yaml](values-production.yaml) has defaults optimized for use in production environments.
### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
## Persistence
The [Bitnami Elasticsearch](https://github.com/bitnami/bitnami-docker-elasticsearch) image stores the Elasticsearch data at the `/bitnami/elasticsearch/data` path of the container.
bitnami/elasticsearch/templates/NOTES.txt
+7
View File
@@ -63,3 +63,10 @@
kubectl port-forward --namespace {{ .Release.Namespace }} svc/{{ template "elasticsearch.coordinating.fullname" . }} {{ .Values.coordinating.service.port }}:9200 &
curl http://127.0.0.1:9200/
{{- end }}
{{- if and (contains "bitnami/" .Values.image.repository) (not (.Values.image.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.image.repository }}:{{ .Values.image.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
bitnami/elasticsearch/templates/coordinating-deploy.yaml
+4
View File
@@ -21,6 +21,10 @@ spec:
app: {{ template "elasticsearch.name" . }}
release: {{ .Release.Name | quote }}
role: "coordinating-only"
{{- with .Values.coordinating.podAnnotations }}
annotations:
{{ toYaml . | indent 8 }}
{{- end }}
spec:
{{- if .Values.securityContext.enabled }}
securityContext:
bitnami/elasticsearch/templates/data-statefulset.yaml
+4
View File
@@ -31,6 +31,10 @@ spec:
chart: {{ template "elasticsearch.chart" . }}
release: {{ .Release.Name | quote }}
role: "data"
{{- with .Values.data.podAnnotations }}
annotations:
{{ toYaml . | indent 8 }}
{{- end }}
spec:
{{- include "elasticsearch.imagePullSecrets" . | nindent 6 }}
{{- if .Values.securityContext.enabled }}
bitnami/elasticsearch/templates/ingest-deploy.yaml
+4
View File
@@ -22,6 +22,10 @@ spec:
app: {{ template "elasticsearch.name" . }}
release: {{ .Release.Name | quote }}
role: "ingest"
{{- with .Values.ingest.podAnnotations }}
annotations:
{{ toYaml . | indent 8 }}
{{- end }}
spec:
{{- include "elasticsearch.imagePullSecrets" . | nindent 6 }}
{{- if .Values.securityContext.enabled }}
bitnami/elasticsearch/templates/master-statefulset.yaml
+5 -1
View File
@@ -23,6 +23,10 @@ spec:
chart: {{ template "elasticsearch.chart" . }}
release: {{ .Release.Name | quote }}
role: "master"
{{- with .Values.master.podAnnotations }}
annotations:
{{ toYaml . | indent 8 }}
{{- end }}
spec:
{{- include "elasticsearch.imagePullSecrets" . | nindent 6 }}
{{- if .Values.securityContext.enabled }}
@@ -133,4 +137,4 @@ spec:
name: {{ template "elasticsearch.fullname" . }}
{{- end }}
- name: "data"
emptyDir: {}
emptyDir: {}
bitnami/elasticsearch/templates/metrics-deploy.yaml
+4
View File
@@ -23,6 +23,10 @@ spec:
release: {{ .Release.Name | quote }}
chart: {{ template "elasticsearch.chart" . }}
role: "metrics"
{{- with .Values.metrics.podAnnotations }}
annotations:
{{ toYaml . | indent 8 }}
{{- end }}
spec:
{{- include "elasticsearch.imagePullSecrets" . | indent 6 }}
containers:
bitnami/elasticsearch/values-production.yaml
+1 -1
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/elasticsearch
tag: 7.0.1
tag: 7.1.1-debian-9-r0
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
bitnami/elasticsearch/values.yaml
+14 -1
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/elasticsearch
tag: 7.0.1
tag: 7.1.1-debian-9-r0
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -85,6 +85,9 @@ master:
annotations: {}
# loadBalancerIP:
## Provide annotations for the master pods.
podAnnotations: {}
## Configure resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
##
@@ -151,6 +154,9 @@ coordinating:
annotations: {}
# loadBalancerIP:
## Provide annotations for the coordinating pods.
podAnnotations: {}
## Configure resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
##
@@ -189,6 +195,8 @@ data:
antiAffinity: "soft"
## node affinity
# nodeAffinity:
## Provide annotations for the data pods.
podAnnotations: {}
## Configure resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
##
@@ -268,6 +276,9 @@ ingest:
annotations: {}
# loadBalancerIP:
## Provide annotations for the ingest pods.
podAnnotations: {}
## Configure resource requests and limits
## ref: http://kubernetes.io/docs/user-guide/compute-resources/
##
@@ -306,6 +317,8 @@ metrics:
##
# pullSecrets:
# - myRegistryKeySecretName
## Provide annotations for the metrics pods.
podAnnotations: {}
annotations:
prometheus.io/scrape: "true"
prometheus.io/port: "9108"
bitnami/etcd/Chart.yaml
+1 -1
View File
@@ -1,6 +1,6 @@
apiVersion: v1
name: etcd
version: 2.2.3
version: 2.2.5
appVersion: 3.3.13
description: etcd is a distributed key value store that provides a reliable way to store data across a cluster of machines
keywords:
bitnami/etcd/README.md
+7 -1
View File
@@ -51,7 +51,7 @@ The following tables lists the configurable parameters of the etcd chart and the
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.registry` | etcd image registry | `docker.io` |
| `image.repository` | etcd Image name | `bitnami/etcd` |
| `image.tag` | etcd Image tag | `{VERSION}` |
| `image.tag` | etcd Image tag | `{TAG_NAME}` |
| `image.pullPolicy` | etcd image pull policy | `Always` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.debug` | Specify if debug values should be set | `false` |
@@ -127,6 +127,12 @@ $ helm install --name my-release -f values.yaml bitnami/etcd
> **Tip**: You can use the default [values.yaml](values.yaml)
### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
### Using custom configuration
In order to use custom configuration parameters, two options are available:
bitnami/etcd/templates/NOTES.txt
+7
View File
@@ -75,3 +75,10 @@ To connect to your etcd server from outside the cluster execute the following co
{{ if .Values.auth.client.enableAuthentication }}
* As TLS host authentication is enabled you should add the flag `--ca-file /opt/bitnami/etcd/certs/client/ca.crt` to the etcdctl commands.
{{- end }}
{{- if and (contains "bitnami/" .Values.image.repository) (not (.Values.image.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.image.repository }}:{{ .Values.image.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
bitnami/etcd/values-production.yaml
+1 -1
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/etcd
tag: 3.3.13
tag: 3.3.13-debian-9-r16
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
bitnami/etcd/values.yaml
+1 -1
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/etcd
tag: 3.3.13
tag: 3.3.13-debian-9-r16
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
bitnami/external-dns/Chart.yaml
+2 -2
View File
@@ -1,7 +1,7 @@
apiVersion: v1
name: external-dns
version: 1.5.3
appVersion: 0.5.13
version: 1.5.6
appVersion: 0.5.14
description: ExternalDNS is a Kubernetes addon that configures public DNS servers with information about exposed Kubernetes services to make them discoverable.
keywords:
- external-dns
bitnami/external-dns/README.md
+7 -1
View File
@@ -52,7 +52,7 @@ The following table lists the configurable parameters of the external-dns chart
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.registry` | ExternalDNS image registry | `docker.io` |
| `image.repository` | ExternalDNS Image name | `bitnami/external-dns` |
| `image.tag` | ExternalDNS Image tag | `{VERSION}` |
| `image.tag` | ExternalDNS Image tag | `{TAG_NAME}` |
| `image.pullPolicy` | ExternalDNS image pull policy | `Always` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.debug` | Specify if debug values should be set | `false` |
@@ -124,6 +124,12 @@ $ helm install --name my-release -f values.yaml bitnami/external-dns
> **Tip**: You can use the default [values.yaml](values.yaml)
### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
## Tutorials
Find information about the requirements for each DNS provider on the link below:
bitnami/external-dns/templates/NOTES.txt
+7
View File
@@ -43,3 +43,10 @@ Replace the placeholder YOUR_DNS_PROVIDER with a valid DNS provider (aws, azure,
{{- end }}
** Please be patient while the chart is being deployed **
{{- if and (contains "bitnami/" .Values.image.repository) (not (.Values.image.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.image.repository }}:{{ .Values.image.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
bitnami/external-dns/values-production.yaml
+1 -1
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/external-dns
tag: 0.5.13
tag: 0.5.14-debian-9-r14
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
bitnami/external-dns/values.yaml
+1 -1
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/external-dns
tag: 0.5.13
tag: 0.5.14-debian-9-r14
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
bitnami/jenkins/Chart.yaml
+1 -1
View File
@@ -1,6 +1,6 @@
apiVersion: v1
name: jenkins
version: 2.3.2
version: 2.3.4
appVersion: 2.164.3
description: The leading open source automation server
keywords:
bitnami/jenkins/README.md
+7 -1
View File
@@ -51,7 +51,7 @@ The following tables lists the configurable parameters of the Jenkins chart and
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.registry` | Jenkins image registry | `docker.io` |
| `image.repository` | Jenkins Image name | `bitnami/jenkins` |
| `image.tag` | Jenkins Image tag | `{VERSION}` |
| `image.tag` | Jenkins Image tag | `{TAG_NAME}` |
| `image.pullPolicy` | Jenkins image pull policy | `Always` if `imageTag` is `latest`, else `IfNotPresent` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `jenkinsUser` | User of the application | `user` |
@@ -113,6 +113,12 @@ $ helm install --name my-release -f values.yaml bitnami/jenkins
> **Tip**: You can use the default [values.yaml](values.yaml)
### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
## Persistence
The [Bitnami Jenkins](https://github.com/bitnami/bitnami-docker-jenkins) image stores the Jenkins data and configurations at the `/bitnami/jenkins` path of the container.
bitnami/jenkins/templates/NOTES.txt
+7
View File
@@ -29,3 +29,10 @@
echo Username: {{ .Values.jenkinsUser }}
echo Password: $(kubectl get secret --namespace {{ .Release.Namespace }} {{ template "fullname" . }} -o jsonpath="{.data.jenkins-password}" | base64 --decode)
{{- if and (contains "bitnami/" .Values.image.repository) (not (.Values.image.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.image.repository }}:{{ .Values.image.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
bitnami/jenkins/values.yaml
+1 -1
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/jenkins
tag: 2.164.3
tag: 2.164.3-debian-9-r16
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
bitnami/kafka/Chart.yaml
+1 -1
View File
@@ -1,6 +1,6 @@
apiVersion: v1
name: kafka
version: 2.2.4
version: 2.2.5
appVersion: 2.2.0
description: Apache Kafka is a distributed streaming platform.
keywords:
bitnami/kafka/README.md
+10 -1
View File
@@ -51,12 +51,15 @@ The following tables lists the configurable parameters of the Kafka chart and th
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.registry` | Kafka image registry | `docker.io` |
| `image.repository` | Kafka Image name | `bitnami/kafka` |
| `image.tag` | Kafka Image tag | `{VERSION}` |
| `image.tag` | Kafka Image tag | `{TAG_NAME}` |
| `image.pullPolicy` | Kafka image pull policy | `Always` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.debug` | Specify if debug values should be set | `false` |
| `nameOverride` | String to partially override kafka.fullname template with a string (will append the release name) | `nil` |
| `fullnameOverride` | String to fully override kafka.fullname template with a string | `nil` |
| `updateStrategy` | Update strategy for the stateful set | `RollingUpdate` |
| `rollingUpdatePartition` | Partition update strategy | `nil` |
| `podDisruptionBudget.maxUnavailable` | Max number of pods down simultaneously | `1` |
| `replicaCount` | Number of Kafka nodes | `1` |
| `config` | Configuration file for Kafka | `nil` |
| `allowPlaintextListener` | Allow to use the PLAINTEXT listener | `true` |
@@ -170,6 +173,12 @@ $ helm install --name my-release -f values.yaml bitnami/kafka
> **Tip**: You can use the default [values.yaml](values.yaml)
### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
## Production and horizontal scaling
The following repo contains the recommended production settings for Kafka server in an alternative [values file](values-production.yaml). Please read carefully the comments in the values-production.yaml file to set up your environment
bitnami/kafka/templates/NOTES.txt
+7
View File
@@ -91,3 +91,10 @@ To connect to your Kafka server from outside the cluster execute the following c
CONSUMER:
kafka-console-consumer.sh --bootstrap-server 127.0.0.1:9092 --topic test --from-beginning
{{ end }}
{{- if and (contains "bitnami/" .Values.image.repository) (not (.Values.image.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.image.repository }}:{{ .Values.image.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
bitnami/kafka/templates/poddisruptionbudget.yaml
+20
View File
@@ -0,0 +1,20 @@
{{- $replicaCount := int .Values.replicaCount }}
{{- if gt $replicaCount 1 }}
apiVersion: policy/v1beta1
kind: PodDisruptionBudget
metadata:
name: {{ template "kafka.fullname" . }}
labels:
app.kubernetes.io/name: {{ template "kafka.name" . }}
helm.sh/chart: {{ template "kafka.chart" . }}
app.kubernetes.io/instance: {{ .Release.Name }}
app.kubernetes.io/managed-by: {{ .Release.Service }}
app.kubernetes.io/component: kafka
spec:
selector:
matchLabels:
app.kubernetes.io/name: {{ template "kafka.name" . }}
app.kubernetes.io/instance: {{ .Release.Name }}
app.kubernetes.io/component: kafka
{{ toYaml .Values.podDisruptionBudget | indent 2 }}
{{- end }}
bitnami/kafka/values-production.yaml
+16 -2
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/kafka
tag: 2.2.0
tag: 2.2.0-debian-9-r40
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -31,6 +31,12 @@ image:
## ref: https://github.com/bitnami/minideb-extras/#turn-on-bash-debugging
debug: false
## String to partially override kafka.fullname template (will maintain the release name)
# nameOverride:
## String to fully override kafka.fullname template
# fullnameOverride:
## StatefulSet controller supports automated updates. There are two valid update strategies: RollingUpdate and OnDelete
## ref: https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#updating-statefulsets
##
@@ -41,6 +47,14 @@ updateStrategy: RollingUpdate
##
# rollingUpdatePartition:
## Limits the number of pods of the replicated application that are down simultaneously from voluntary disruptions
## The PDB will only be created if replicaCount is greater than 1
## ref: https://kubernetes.io/docs/concepts/workloads/pods/disruptions
##
podDisruptionBudget:
maxUnavailable: 1
replicaCount: 3
config: |-
@@ -153,7 +167,7 @@ socketSendBufferBytes: 102400
zookeeperConnectionTimeoutMs: 6000
## The endpoint identification algorithm to validate server hostname using server certificate.
sslEndpointIdentificationAlgorithm : https
sslEndpointIdentificationAlgorithm: https
## Authentication parameteres
## https://github.com/bitnami/bitnami-docker-kafka#security
bitnami/kafka/values.yaml
+16 -2
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/kafka
tag: 2.2.0
tag: 2.2.0-debian-9-r40
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -31,6 +31,12 @@ image:
## ref: https://github.com/bitnami/minideb-extras/#turn-on-bash-debugging
debug: false
## String to partially override kafka.fullname template (will maintain the release name)
# nameOverride:
## String to fully override kafka.fullname template
# fullnameOverride:
## StatefulSet controller supports automated updates. There are two valid update strategies: RollingUpdate and OnDelete
## ref: https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#updating-statefulsets
##
@@ -41,6 +47,14 @@ updateStrategy: RollingUpdate
##
# rollingUpdatePartition:
## Limits the number of pods of the replicated application that are down simultaneously from voluntary disruptions
## The PDB will only be created if replicaCount is greater than 1
## ref: https://kubernetes.io/docs/concepts/workloads/pods/disruptions
##
podDisruptionBudget:
maxUnavailable: 1
replicaCount: 1
config: |-
@@ -153,7 +167,7 @@ socketSendBufferBytes: 102400
zookeeperConnectionTimeoutMs: 6000
## The endpoint identification algorithm to validate server hostname using server certificate.
sslEndpointIdentificationAlgorithm : https
sslEndpointIdentificationAlgorithm: https
## Authentication parameteres
## https://github.com/bitnami/bitnami-docker-kafka#security
bitnami/kubeapps/Chart.yaml
+2 -2
View File
@@ -1,7 +1,7 @@
apiVersion: v1
name: kubeapps
version: 1.6.2
appVersion: v1.3.2
version: 1.7.0
appVersion: v1.4.0
description: Kubeapps is a dashboard for your Kubernetes cluster that makes it easy to deploy and manage applications in your cluster using Helm
icon: https://raw.githubusercontent.com/kubeapps/kubeapps/master/docs/img/logo.png
keywords:
bitnami/kubeapps/templates/apprepositories.yaml
+8
View File
@@ -4,11 +4,19 @@ kind: AppRepository
metadata:
name: {{ .name }}
annotations:
{{- if semverCompare ">=2.14.0" $.Capabilities.TillerVersion.SemVer }}
# Using the hook pre-install because since Helm v2.14 the crd-install
# hook should be used only for CRDs and the issues related to install
# Custom Resources have been already fixed
# https://github.com/helm/helm/issues/5756#issuecomment-493653454
"helm.sh/hook": pre-install
{{- else }}
# Using the hook crd-install to avoid issue w/Helm v1.11
# https://github.com/kubeapps/kubeapps/pull/955#pullrequestreview-200764260
"helm.sh/hook": crd-install
# Make sure this runs after the AppRepository CRD install
"helm.sh/hook-weight": "10"
{{- end }}
labels:
app: {{ template "kubeapps.apprepository.fullname" $ }}
chart: {{ template "kubeapps.chart" $ }}
bitnami/kubeapps/templates/apprepository-crd.yaml
+1
View File
@@ -14,6 +14,7 @@ metadata:
heritage: {{ .Release.Service }}
spec:
group: kubeapps.com
scope: Namespaced
names:
kind: AppRepository
plural: apprepositories
bitnami/kubeapps/values.yaml
+3 -3
View File
@@ -99,7 +99,7 @@ apprepository:
image:
registry: docker.io
repository: bitnami/kubeapps-apprepository-controller
tag: 1.3.2
tag: 1.4.0
# Image used to perform chart repository syncs
syncImage:
registry: docker.io
@@ -154,7 +154,7 @@ tillerProxy:
image:
registry: docker.io
repository: bitnami/kubeapps-tiller-proxy
tag: 1.3.2
tag: 1.4.0
service:
port: 8080
host: tiller-deploy.kube-system:44134
@@ -216,7 +216,7 @@ dashboard:
image:
registry: docker.io
repository: bitnami/kubeapps-dashboard
tag: 1.3.2
tag: 1.4.0
service:
port: 8080
livenessProbe:
bitnami/memcached/Chart.yaml
+2 -2
View File
@@ -1,7 +1,7 @@
apiVersion: v1
name: memcached
version: 1.5.3
appVersion: 1.5.14
version: 1.5.7
appVersion: 1.5.16
description: Chart for Memcached
keywords:
- memcached
bitnami/memcached/README.md
+7 -1
View File
@@ -51,7 +51,7 @@ The following tables lists the configurable parameters of the Memcached chart an
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.registry` | Memcached image registry | `docker.io` |
| `image.repository` | Memcached Image name | `bitnami/memcached` |
| `image.tag` | Memcached Image tag | `{VERSION}` |
| `image.tag` | Memcached Image tag | `{TAG_NAME}` |
| `image.pullPolicy` | Memcached image pull policy | `Always` if `imageTag` is `latest`, else `IfNotPresent` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `securityContext.enabled` | Enable security context | `true` |
@@ -89,6 +89,12 @@ $ helm install --name my-release -f values.yaml bitnami/memcached
> **Tip**: You can use the default [values.yaml](values.yaml)
### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
## Upgrading
### To 1.0.0
bitnami/memcached/templates/NOTES.txt
+6
View File
@@ -3,3 +3,9 @@
Memcached can be accessed on port 11211 on the following DNS name from within your cluster: {{ template "fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local
{{- if and (contains "bitnami/" .Values.image.repository) (not (.Values.image.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.image.repository }}:{{ .Values.image.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
bitnami/memcached/values-production.yaml
+1 -1
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/memcached
tag: 1.5.14
tag: 1.5.16-debian-9-r3
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
bitnami/memcached/values.yaml
+1 -1
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/memcached
tag: 1.5.14
tag: 1.5.16-debian-9-r3
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
bitnami/metrics-server/Chart.yaml
+1 -1
View File
@@ -1,6 +1,6 @@
apiVersion: v1
name: metrics-server
version: 2.3.4
version: 2.3.6
appVersion: 0.3.3
description: Metrics Server is a cluster-wide aggregator of resource usage data. Metrics Server collects metrics from the Summary API, exposed by Kubelet on each node.
keywords:
bitnami/metrics-server/README.md
+7 -1
View File
@@ -51,7 +51,7 @@ The following tables lists the configurable parameters of the Metrics Server cha
| `global.imagePullSecrets`| Global Docker registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.registry` | Metrics Server image registry | `docker.io` |
| `image.repository` | Metrics Server image name | `bitnami/metrics-server` |
| `image.tag` | Metrics Server image tag | `{VERSION}` |
| `image.tag` | Metrics Server image tag | `{TAG_NAME}` |
| `image.pullPolicy` | Metrics Server image pull policy | `Always` |
| `securePort` | Port where metrics-server will be running | `8443` |
| `service.type` | Kubernetes Service type | `ClusterIP` |
@@ -81,6 +81,12 @@ $ helm install --name my-release -f values.yaml bitnami/metrics-server
> **Tip**: You can use the default [values.yaml](values.yaml)
### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
## Enable security for Metrics Server
### Configure RBAC
bitnami/metrics-server/templates/NOTES.txt
+7
View File
@@ -24,3 +24,10 @@ Option B:
You configure the metrics API service outside of this Helm chart
{{- end -}}
{{- if and (contains "bitnami/" .Values.image.repository) (not (.Values.image.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.image.repository }}:{{ .Values.image.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
bitnami/metrics-server/values.yaml
+1 -1
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/metrics-server
tag: 0.3.3
tag: 0.3.3-debian-9-r16
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
bitnami/minio/Chart.yaml
+2 -2
View File
@@ -1,6 +1,6 @@
apiVersion: v1
version: 0.1.1
appVersion: 2019.5.2
version: 0.1.6
appVersion: 2019.5.23
description: MinIO is an object storage server, compatible with Amazon S3 cloud storage service, mainly used for storing unstructured data (such as photos, videos, log files, etc.)
keywords:
- minio
bitnami/minio/README.md
+8 -2
View File
@@ -54,13 +54,13 @@ The following table lists the configurable parameters of the MinIO chart and the
| `global.minio.secretKey` | MinIO Secret Key (overrides `secretKey.password`) | `nil` |
| `image.registry` | MinIO image registry | `docker.io` |
| `image.repository` | MinIO image name | `bitnami/minio` |
| `image.tag` | MinIO image tag | `{VERSION}` |
| `image.tag` | MinIO image tag | `{TAG_NAME}` |
| `image.pullPolicy` | Image pull policy | `Always` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.debug` | Specify if debug logs should be enabled | `false` |
| `clientImage.registry` | MinIO Client image registry | `docker.io` |
| `clientImage.repository` | MinIO Client image name | `bitnami/minio-client` |
| `clientImage.tag` | MinIO Client image tag | `{VERSION}` |
| `clientImage.tag` | MinIO Client image tag | `{TAG_NAME}` |
| `mode` | MinIO server mode (`standalone` or `distributed`) | `standalone` |
| `statefulset.replicaCount` | Number of pods (only for Minio distributed mode). Should be 4 <= x <= 32 | `4` |
| `statefulset.updateStrategy` | Statefulset update strategy policy | `RollingUpdate` |
@@ -136,6 +136,12 @@ $ helm install --name my-release -f values.yaml bitnami/minio
> **Tip**: You can use the default [values.yaml](values.yaml)
### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
## Distributed mode
You can start the MinIO chart in distributed mode with the following command:
bitnami/minio/templates/NOTES.txt
+1
View File
@@ -68,3 +68,4 @@ To access the MinIO web UI:
{{- end }}
{{ include "minio.validateValues" . }}
{{ include "minio.checkRollingTags" . }}
bitnami/minio/templates/_helpers.tpl
+12
View File
@@ -140,3 +140,15 @@ minio: replicaCount
Please set a valid number of replicas (--set statefulset.replicaCount=X)
{{- end -}}
{{- end -}}
{{/* Check if there are rolling tags in the images */}}
{{- define "minio.checkRollingTags" -}}
{{- if and (contains "bitnami/" .Values.image.repository) (not (.Values.image.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.image.repository }}:{{ .Values.image.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
{{- if and (contains "bitnami/" .Values.clientImage.repository) (not (.Values.clientImage.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.clientImage.repository }}:{{ .Values.clientImage.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
{{- end -}}
bitnami/minio/templates/deployment-standalone.yaml
+1 -1
View File
@@ -89,7 +89,7 @@ spec:
value: {{ .Values.defaultBuckets }}
{{- end }}
- name: MINIO_BROWSER
value: {{ ternary "off" "on" .Values.disableWebUI }}
value: {{ ternary "off" "on" .Values.disableWebUI | quote }}
{{- if .Values.extraEnv }}
{{ toYaml .Values.extraEnv | indent 8 }}
{{- end }}
bitnami/minio/templates/statefulset.yaml
+1 -1
View File
@@ -104,7 +104,7 @@ spec:
key: secret-key
{{- end }}
- name: MINIO_BROWSER
value: {{ ternary "off" "on" .Values.disableWebUI }}
value: {{ ternary "off" "on" .Values.disableWebUI | quote }}
{{- if .Values.extraEnv }}
{{ toYaml .Values.extraEnv | indent 8 }}
{{- end }}
bitnami/minio/values-production.yaml
+2 -2
View File
@@ -18,7 +18,7 @@ global:
image:
registry: docker.io
repository: bitnami/minio
tag: 2019.5.2
tag: 2019.5.23-debian-9-r0
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -42,7 +42,7 @@ image:
clientImage:
registry: docker.io
repository: bitnami/minio-client
tag: latest
tag: 2019.5.23-debian-9-r5
## MinIO server mode. Allowed values: standalone or distributed.
## Distributed Minio ref: https://docs.minio.io/docs/distributed-minio-quickstart-guide
bitnami/minio/values.yaml
+2 -2
View File
@@ -18,7 +18,7 @@ global:
image:
registry: docker.io
repository: bitnami/minio
tag: 2019.5.2
tag: 2019.5.23-debian-9-r0
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -42,7 +42,7 @@ image:
clientImage:
registry: docker.io
repository: bitnami/minio-client
tag: latest
tag: 2019.5.23-debian-9-r5
## MinIO server mode. Allowed values: standalone or distributed.
## Distributed Minio ref: https://docs.minio.io/docs/distributed-minio-quickstart-guide
bitnami/mysql/Chart.yaml
+2 -2
View File
@@ -1,7 +1,7 @@
apiVersion: v1
name: mysql
version: 4.5.2
appVersion: 5.7.26
version: 5.0.3
appVersion: 8.0.16
description: Chart to create a Highly available MySQL cluster
keywords:
- mysql
bitnami/mysql/README.md
+7 -1
View File
@@ -51,7 +51,7 @@ The following tables lists the configurable parameters of the MySQL chart and th
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.registry` | MySQL image registry | `docker.io` |
| `image.repository` | MySQL Image name | `bitnami/mysql` |
| `image.tag` | MySQL Image tag | `{VERSION}` |
| `image.tag` | MySQL Image tag | `{TAG_NAME}` |
| `image.pullPolicy` | MySQL image pull policy | `Always` if `imageTag` is `latest`, else `IfNotPresent` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `service.type` | Kubernetes service type | `ClusterIP` |
@@ -138,6 +138,12 @@ $ helm install --name my-release -f values.yaml bitnami/mysql
> **Tip**: You can use the default [values.yaml](values.yaml)
### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
## Initialize a fresh instance
The [Bitnami MySQL](https://github.com/bitnami/bitnami-docker-mysql) image allows you to use your custom scripts to initialize a fresh instance. In order to execute the scripts, they must be located inside the chart folder `files/docker-entrypoint-initdb.d` so they can be consumed as a ConfigMap.
bitnami/mysql/templates/NOTES.txt
+7
View File
@@ -40,3 +40,10 @@ To upgrade this helm chart:
ROOT_PASSWORD=$(kubectl get secret --namespace {{ .Release.Namespace }} {{ template "fullname" . }} -o jsonpath="{.data.mysql-root-password}" | base64 --decode)
helm upgrade {{ .Release.Name }} bitnami/mysql --set root.password=$ROOT_PASSWORD
{{- if and (contains "bitnami/" .Values.image.repository) (not (.Values.image.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.image.repository }}:{{ .Values.image.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
bitnami/mysql/values-production.yaml
+1 -1
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/mysql
tag: 5.7.26
tag: 8.0.16-debian-9-r16
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
bitnami/mysql/values.yaml
+1 -1
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/mysql
tag: 5.7.26
tag: 8.0.16-debian-9-r16
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
bitnami/nginx-ingress-controller/Chart.yaml
+1 -1
View File
@@ -1,6 +1,6 @@
apiVersion: v1
name: nginx-ingress-controller
version: 3.4.5
version: 3.4.7
appVersion: 0.24.1
description: Chart for the nginx Ingress controller
keywords:
bitnami/nginx-ingress-controller/README.md
+7 -1
View File
@@ -53,7 +53,7 @@ Parameter | Description | Default
`name` | name of the controller component | `controller`
`image.registry` | name of the container image registry | `docker.io`
`image.repository` | controller container image repository | `bitnami/nginx-ingress-controller`
`image.tag` | controller container image tag | `{VERSION}`
`image.tag` | controller container image tag | `{TAG_NAME}`
`image.pullPolicy` | controller container image pull policy | `IfNotPresent`
`config` | nginx ConfigMap entries | `use-geoip: "false", use-geoip2: "true"`
`hostNetwork` | If the nginx deployment / daemonset should run on the host's network namespace. Do not set this when `controller.service.externalIPs` is set and `kube-proxy` is used as there will be a port-conflict for port `80` | false
@@ -182,6 +182,12 @@ $ helm install --name my-release -f values.yaml bitnami/nginx-ingress-controller
> **Tip**: You can use the default [values.yaml](values.yaml)
### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
## Upgrading
### To 1.0.0
bitnami/nginx-ingress-controller/templates/NOTES.txt
+7
View File
@@ -64,3 +64,10 @@ If TLS is enabled for the Ingress, a Secret containing the certificate and key m
tls.crt: <base64 encoded cert>
tls.key: <base64 encoded key>
type: kubernetes.io/tls
{{- if and (contains "bitnami/" .Values.image.repository) (not (.Values.image.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.image.repository }}:{{ .Values.image.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
bitnami/nginx-ingress-controller/values-production.yaml
+4 -3
View File
@@ -13,7 +13,7 @@ name: controller
image:
registry: docker.io
repository: bitnami/nginx-ingress-controller
tag: 0.24.1
tag: 0.24.1-debian-9-r25
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -309,8 +309,9 @@ defaultBackend:
name: default-backend
image:
repository: k8s.gcr.io/defaultbackend
tag: "1.4"
registry: docker.io
repository: bitnami/nginx
tag: 1.16.0-debian-9-r26
pullPolicy: IfNotPresent
## Optionally specify an array of imagePullSecrets.
## Secrets must be manually created in the namespace.
bitnami/nginx-ingress-controller/values.yaml
+2 -2
View File
@@ -13,7 +13,7 @@ name: controller
image:
registry: docker.io
repository: bitnami/nginx-ingress-controller
tag: 0.24.1
tag: 0.24.1-debian-9-r25
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -310,7 +310,7 @@ defaultBackend:
image:
registry: docker.io
repository: bitnami/nginx
tag: latest
tag: 1.16.0-debian-9-r26
pullPolicy: Always
## Optionally specify an array of imagePullSecrets.
## Secrets must be manually created in the namespace.
bitnami/nginx/Chart.yaml
+1 -1
View File
@@ -1,6 +1,6 @@
apiVersion: v1
name: nginx
version: 3.2.0
version: 3.2.2
appVersion: 1.16.0
description: Chart for the nginx server
keywords:
bitnami/nginx/README.md
+7 -1
View File
@@ -48,7 +48,7 @@ The following tables lists the configurable parameters of the NGINX Open Source
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.registry` | NGINX image registry | `docker.io` |
| `image.repository` | NGINX Image name | `bitnami/nginx` |
| `image.tag` | NGINX Image tag | `{VERSION}` |
| `image.tag` | NGINX Image tag | `{TAG_NAME}` |
| `image.pullPolicy` | NGINX image pull policy | `Always` if `imageTag` is `latest`, else `IfNotPresent` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `serverBlock` | Custom NGINX server block | `nil` |
@@ -96,6 +96,12 @@ $ helm install --name my-release -f values.yaml bitnami/nginx
> **Tip**: You can use the default [values.yaml](values.yaml)
### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
### Providing a custom server block
You can use the `serverBlock` value to provide a custom server block for NGINX to use.
bitnami/nginx/templates/NOTES.txt
+6
View File
@@ -0,0 +1,6 @@
{{- if and (contains "bitnami/" .Values.image.repository) (not (.Values.image.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.image.repository }}:{{ .Values.image.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
bitnami/nginx/values.yaml
+2 -2
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/nginx
tag: 1.16.0
tag: 1.16.0-debian-9-r26
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -32,7 +32,7 @@ image:
service:
type: LoadBalancer
## Provide optional annotations to the service i.e. for external-dns
# annotations:
# annotations:
# external-dns.alpha.kubernetes.io/hostname: yourservicename.k8s.yourcompany.com
##
## HTTP Port
bitnami/node/Chart.yaml
+2 -2
View File
@@ -1,7 +1,7 @@
apiVersion: v1
name: node
version: 8.1.5
appVersion: 10.15.3
version: 8.1.8
appVersion: 10.16.0
description: Event-driven I/O server-side JavaScript environment based on V8
keywords:
- node
bitnami/node/README.md
+7 -1
View File
@@ -56,7 +56,7 @@ The following table lists the configurable parameters of the Node chart and thei
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.registry` | NodeJS image registry | `docker.io` |
| `image.repository` | NodeJS image name | `bitnami/node` |
| `image.tag` | NodeJS image tag | `{VERSION}` |
| `image.tag` | NodeJS image tag | `{TAG_NAME}` |
| `image.pullPolicy` | NodeJS image pull policy | `IfNotPresent` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `git.registry` | Git image registry | `docker.io` |
@@ -115,6 +115,12 @@ $ helm install --name my-release -f values.yaml bitnami/node
> **Tip**: You can use the default [values.yaml](values.yaml)
### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
## Persistence
The [Bitnami Node](https://github.com/bitnami/bitnami-docker-node) image stores the Node application and configurations at the `/app` path of the container.
bitnami/node/templates/NOTES.txt
+2
View File
@@ -21,3 +21,5 @@
echo "Node app URL: http://127.0.0.1:{{ .Values.service.port }}/"
{{- end }}
{{ include "node.checkRollingTags" . }}
bitnami/node/templates/_helpers.tpl
+12
View File
@@ -121,3 +121,15 @@ imagePullSecrets:
{{- end }}
{{- end -}}
{{- end -}}
{{/* Check if there are rolling tags in the images */}}
{{- define "node.checkRollingTags" -}}
{{- if and (contains "bitnami/" .Values.image.repository) (not (.Values.image.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.image.repository }}:{{ .Values.image.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
{{- if and (contains "bitnami/" .Values.git.repository) (not (.Values.git.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.git.repository }}:{{ .Values.git.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
{{- end -}}
bitnami/node/values.yaml
+2 -2
View File
@@ -13,7 +13,7 @@
image:
registry: docker.io
repository: bitnami/node
tag: 10.15.3
tag: 10.16.0-debian-9-r0
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -32,7 +32,7 @@ image:
git:
registry: docker.io
repository: bitnami/git
tag: latest
tag: 2.21.0-debian-9-r72
pullPolicy: IfNotPresent
## Optionally specify an array of imagePullSecrets.
## Secrets must be manually created in the namespace.
bitnami/pytorch/.helmignore
+22
View File
@@ -0,0 +1,22 @@
# Patterns to ignore when building packages.
# This supports shell glob matching, relative path matching, and
# negation (prefixed with !). Only one pattern per line.
.DS_Store
# Common VCS dirs
.git/
.gitignore
.bzr/
.bzrignore
.hg/
.hgignore
.svn/
# Common backup files
*.swp
*.bak
*.tmp
*~
# Various IDEs
.project
.idea/
*.tmproj
.vscode/
bitnami/pytorch/Chart.yaml
+18
View File
@@ -0,0 +1,18 @@
apiVersion: v1
name: pytorch
version: 0.0.4
appVersion: 1.1.0
description: Deep learning platform that accelerates the transition from research prototyping to production deployment
keywords:
- pytorch
- python
- machine
- learning
home: http://pytorch.org/
sources:
- https://github.com/bitnami/bitnami-docker-pytorch
maintainers:
- name: Bitnami
email: containers@bitnami.com
engine: gotpl
icon: https://bitnami.com/assets/stacks/pytorch/img/pytorch-stack-110x117.png
bitnami/pytorch/README.md
+164
View File
@@ -0,0 +1,164 @@
# PyTorch
[PyTorch](http://pytorch.org/) is a deep learning platform that accelerates the transition from research prototyping to production deployment. It is built for full integration into Python that enables you to use it with its libraries and main packages.
## TL;DR;
```console
$ helm install bitnami/pytorch
```
## Introduction
This chart bootstraps a [PyTorch](https://github.com/bitnami/bitnami-docker-pytorch) deployment on a [Kubernetes](http://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment and management of Helm Charts in clusters. This Helm chart has been tested on top of [Bitnami Kubernetes Production Runtime](https://kubeprod.io/) (BKPR). Deploy BKPR to get automated TLS certificates, logging and monitoring for your applications.
## Prerequisites
- Kubernetes 1.8+ with Beta APIs enabled
- PV provisioner support in the underlying infrastructure
## Installing the Chart
To install the chart with the release name `my-release`:
```console
$ helm install --name my-release bitnami/pytorch
```
The command deploys PyTorch on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured.
> **Tip**: List all releases using `helm list`
## Uninstalling the Chart
To uninstall/delete the `my-release` deployment:
```console
$ helm delete my-release
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
## Configuration
The following table lists the configurable parameters of the MinIO chart and their default values.
| Parameter | Description | Default |
| ------------------------------------ | -------------------------------------------------------------------------------------------- | ------------------------------------------------------- |
| `global.imageRegistry` | Global Docker image registry | `nil` |
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.registry` | PyTorch image registry | `docker.io` |
| `image.repository` | PyTorch image name | `bitnami/pytorch` |
| `image.tag` | PyTorch image tag | `{TAG_NAME}` |
| `image.pullPolicy` | Image pull policy | `IfNotPresent` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| `image.debug` | Specify if debug logs should be enabled | `false` |
| `git.registry` | Git image registry | `docker.io` |
| `git.repository` | Git image name | `bitnami/git` |
| `git.tag` | Git image tag | `latest` |
| `git.pullPolicy` | Git image pull policy | `Always` |
| `git.pullSecrets` | Specify docker-registry secret names as an array | `[]` (does not add image pull secrets to deployed pods) |
| service.type | Kubernetes service type | `ClusterIP` |
| `entrypoint.file` | Main entrypoint to your application | `''` |
| `entrypoint.args` | Args required by your entrypoint | `nil` |
| `mode` | Run PyTorch in standalone or distributed mode (possible values: `standalone`, `distributed`) | `standalone` |
| `worldSize` | Number of nodes that will execute your code | `nil` |
| `port` | PyTorch master port | `49875` |
| `configMap` | Config map that contains the files you want to load in PyTorch | `nil` |
| `cloneFilesFromGit.enabled` | Enable in order to download files from git repository | `false` |
| `cloneFilesFromGit.repository` | Repository that holds the files | `nil` |
| `cloneFilesFromGit.revision` | Revision from the repository to checkout | `master` |
| `extraEnvVars` | Extra environment variables to add to master and workers pods | `nil` |
| `nodeSelector` | Node labels for pod assignment | `{}` |
| `tolerations` | Toleration labels for pod assignment | `[]` |
| `affinity` | Map of node/pod affinities | `{}` |
| `resources` | Pod resources | `{}` |
| `securityContext.enabled` | Enable security context | `true` |
| `securityContext.fsGroup` | Group ID for the container | `1001` |
| `securityContext.runAsUser` | User ID for the container | `1001` |
| `livenessProbe.enabled` | Enable/disable the Liveness probe | `true` |
| `livenessProbe.initialDelaySeconds` | Delay before liveness probe is initiated | `5` |
| `livenessProbe.periodSeconds` | How often to perform the probe | `5` |
| `livenessProbe.timeoutSeconds` | When the probe times out | `5` |
| `livenessProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed. | `1` |
| `livenessProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded. | `5` |
| `readinessProbe.enabled` | Enable/disable the Readiness probe | `true` |
| `readinessProbe.initialDelaySeconds` | Delay before readiness probe is initiated | `5` |
| `readinessProbe.periodSeconds` | How often to perform the probe | `5` |
| `readinessProbe.timeoutSeconds` | When the probe times out | `1` |
| `readinessProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed. | `1` |
| `readinessProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded. | `5` |
| `persistence.enabled` | Use a PVC to persist data | `true` |
| `persistence.mountPath` | Path to mount the volume at | `/bitnami/pytorch` |
| `persistence.storageClass` | Storage class of backing PVC | `nil` (uses alpha storage class annotation) |
| `persistence.accessMode` | Use volume as ReadOnly or ReadWrite | `ReadWriteOnce` |
| `persistence.size` | Size of data volume | `8Gi` |
| `persistence.annotations` | Persistent Volume annotations | `{}` |
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
```console
$ helm install --name my-release \
--set mode=distributed \
--set worldSize=4 \
bitnami/pytorch
```
The above command create 4 pods for PyTorch: one master and three workers.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
```console
$ helm install --name my-release -f values.yaml bitnami/pytorch
```
> **Tip**: You can use the default [values.yaml](values.yaml)
### [Rolling VS Immutable tags](https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/)
It is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.
Bitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.
## Loading your files
The PyTorch chart supports three different ways to load your files. In order of priority, they are:
1. Existing config map
2. Files under the `files` directory
3. Cloning a git repository
This means that if you specify a config map with your files, it won't look for the `files/` directory nor the git repository.
In order to use use an existing config map:
```console
$ helm install --name my-release \
--set configMap=my-config-map \
bitnami/pytorch
```
To load your files from the `files/` directory you don't have to set any option. Just copy your files inside and don't specify a `ConfigMap`:
```console
$ helm install --name my-release \
bitnami/pytorch
```
Finally, if you want to clone a git repository:
```console
$ helm install --name my-release \
--set cloneFilesFromGit.enabled=true \
--set cloneFilesFromGit.repository=https://github.com/my-user/my-repo \
--set cloneFilesFromGit.revision=master \
bitnami/pytorch
```
## Persistence
The [Bitnami PyTorch](https://github.com/bitnami/bitnami-docker-pytorch) image can persist data. If enabled, the persisted path is `/bitnami/pytorch` by default.
The chart mounts a [Persistent Volume](http://kubernetes.io/docs/user-guide/persistent-volumes/) at this location. The volume is created using dynamic volume provisioning.
bitnami/pytorch/templates/NOTES.txt
+38
View File
@@ -0,0 +1,38 @@
{{- if or (.Values.configMap) (.Files.Glob "files/*") (.Values.cloneFilesFromGit.enabled) }}
{{- if .Values.entrypoint.file }}
The provided file {{ .Values.entrypoint.file }} is being executed. You can see the logs of each running node with:
kubectl logs [POD_NAME]
and the list of pods:
kubectl get pods --namespace {{ .Release.Namespace }} -l "app.kubernetes.io/name={{ include "pytorch.name" . }},app.kubernetes.io/instance={{ .Release.Name }}"
{{- else }}
You didn't specify any entrypoint to your code.
To run it, you can either deploy again using the `pytorch.entrypoint.file` option to specify your entrypoint, or execute it manually by jumping into the pods:
1. Get the running pods
kubectl get pods --namespace {{ .Release.Namespace }} -l "app.kubernetes.io/name={{ include "pytorch.name" . }},app.kubernetes.io/instance={{ .Release.Name }}"
2. Get into a pod
kubectl exec -ti [POD_NAME] bash
3. Execute your script as you would normally do.
{{- end }}
{{- else }}
WARNING: You haven't loaded any file. You can access the Python REPL by jumping into the pods:
1. Get the running pods
kubectl get pods --namespace {{ .Release.Namespace }} -l "app.kubernetes.io/name={{ include "pytorch.name" . }},app.kubernetes.io/instance={{ .Release.Name }}"
2. Run the Python REPL
kubectl exec -ti [POD_NAME] python
This chart allows three different methods to load your files:
1. Load the files from an existing ConfigMap, using the `configMap` option.
2. Putting your files in a `files` folder in the root of the Chart.
3. Cloning a Git repository with the `cloneFilesFromGit` option.
Examples for the different methods can be found in the README.
{{- end }}
{{ include "pytorch.validateValues" . }}
{{ include "pytorch.checkRollingTags" . }}
bitnami/pytorch/templates/_helpers.tpl
+159
View File
@@ -0,0 +1,159 @@
{{/* vim: set filetype=mustache: */}}
{{/*
Expand the name of the chart.
*/}}
{{- define "pytorch.name" -}}
{{- default .Chart.Name .Values.nameOverride | trunc 63 | trimSuffix "-" -}}
{{- end -}}
{{/*
Create a default fully qualified app name.
We truncate at 63 chars because some Kubernetes name fields are limited to this (by the DNS naming spec).
If release name contains chart name it will be used as a full name.
*/}}
{{- define "pytorch.fullname" -}}
{{- if .Values.fullnameOverride -}}
{{- .Values.fullnameOverride | trunc 63 | trimSuffix "-" -}}
{{- else -}}
{{- $name := default .Chart.Name .Values.nameOverride -}}
{{- if contains $name .Release.Name -}}
{{- .Release.Name | trunc 63 | trimSuffix "-" -}}
{{- else -}}
{{- printf "%s-%s" .Release.Name $name | trunc 63 | trimSuffix "-" -}}
{{- end -}}
{{- end -}}
{{- end -}}
{{/*
Create chart name and version as used by the chart label.
*/}}
{{- define "pytorch.chart" -}}
{{- printf "%s-%s" .Chart.Name .Chart.Version | replace "+" "_" | trunc 63 | trimSuffix "-" -}}
{{- end -}}
{{/*
Return the proper PyTorch image name
*/}}
{{- define "pytorch.image" -}}
{{- $registryName := .Values.image.registry -}}
{{- $repositoryName := .Values.image.repository -}}
{{- $tag := .Values.image.tag | toString -}}
{{/*
Helm 2.11 supports the assignment of a value to a variable defined in a different scope,
but Helm 2.9 and 2.10 doesn't support it, so we need to implement this if-else logic.
Also, we can't use a single if because lazy evaluation is not an option
*/}}
{{- if .Values.global }}
{{- if .Values.global.imageRegistry }}
{{- printf "%s/%s:%s" .Values.global.imageRegistry $repositoryName $tag -}}
{{- else -}}
{{- printf "%s/%s:%s" $registryName $repositoryName $tag -}}
{{- end -}}
{{- else -}}
{{- printf "%s/%s:%s" $registryName $repositoryName $tag -}}
{{- end -}}
{{- end -}}
{{/*
Return the proper git image name
*/}}
{{- define "git.image" -}}
{{- $registryName := .Values.git.registry -}}
{{- $repositoryName := .Values.git.repository -}}
{{- $tag := .Values.git.tag | toString -}}
{{/*
Helm 2.11 supports the assignment of a value to a variable defined in a different scope,
but Helm 2.9 and 2.10 doesn't support it, so we need to implement this if-else logic.
Also, we can't use a single if because lazy evaluation is not an option
*/}}
{{- if .Values.global }}
{{- if .Values.global.imageRegistry }}
{{- printf "%s/%s:%s" .Values.global.imageRegistry $repositoryName $tag -}}
{{- else -}}
{{- printf "%s/%s:%s" $registryName $repositoryName $tag -}}
{{- end -}}
{{- else -}}
{{- printf "%s/%s:%s" $registryName $repositoryName $tag -}}
{{- end -}}
{{- end -}}
{{/*
Return the proper Docker Image Registry Secret Names
*/}}
{{- define "pytorch.imagePullSecrets" -}}
{{/*
Helm 2.11 supports the assignment of a value to a variable defined in a different scope,
but Helm 2.9 and 2.10 does not support it, so we need to implement this if-else logic.
Also, we can not use a single if because lazy evaluation is not an option
*/}}
{{- if .Values.global }}
{{- if .Values.global.imagePullSecrets }}
imagePullSecrets:
{{- range .Values.global.imagePullSecrets }}
- name: {{ . }}
{{- end }}
{{- else if or .Values.image.pullSecrets .Values.git.pullSecrets }}
imagePullSecrets:
{{- range .Values.image.pullSecrets }}
- name: {{ . }}
{{- end }}
{{- range .Values.git.pullSecrets }}
- name: {{ . }}
{{- end }}
{{- end -}}
{{- else if or .Values.image.pullSecrets .Values.git.pullSecrets }}
imagePullSecrets:
{{- range .Values.image.pullSecrets }}
- name: {{ . }}
{{- end }}
{{- range .Values.git.pullSecrets }}
- name: {{ . }}
{{- end }}
{{- end -}}
{{- end -}}
{{/*
Compile all warnings into a single message, and call fail.
*/}}
{{- define "pytorch.validateValues" -}}
{{- $messages := list -}}
{{- $messages := append $messages (include "pytorch.validateValues.mode" .) -}}
{{- $messages := append $messages (include "pytorch.validateValues.worldSize" .) -}}
{{- $messages := without $messages "" -}}
{{- $message := join "\n" $messages -}}
{{- if $message -}}
{{- printf "\nVALUES VALIDATION:\n%s" $message | fail -}}
{{- end -}}
{{- end -}}
{{/* Validate values of PyTorch - must provide a valid mode ("distributed" or "standalone") */}}
{{- define "pytorch.validateValues.mode" -}}
{{- if and (ne .Values.mode "distributed") (ne .Values.mode "standalone") -}}
pytorch: mode
Invalid mode selected. Valid values are "distributed" and
"standalone". Please set a valid mode (--set mode="xxxx")
{{- end -}}
{{- end -}}
{{/* Validate values of PyTorch - number of replicas must be even, greater than 4 and lower than 32 */}}
{{- define "pytorch.validateValues.worldSize" -}}
{{- $replicaCount := int .Values.worldSize }}
{{- if and (eq .Values.mode "distributed") (lt $replicaCount 24) -}}
pytorch: worldSize
World size must be greater than 1 in distributed mode!!
Please set a valid world size (--set worldSize=X)
{{- end -}}
{{- end -}}
{{/* Check if there are rolling tags in the images */}}
{{- define "pytorch.checkRollingTags" -}}
{{- if and (contains "bitnami/" .Values.image.repository) (not (.Values.image.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.image.repository }}:{{ .Values.image.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
{{- if and (contains "bitnami/" .Values.git.repository) (not (.Values.git.tag | toString | regexFind "-r\\d+$|sha256:")) }}
WARNING: Rolling tag detected ({{ .Values.git.repository }}:{{ .Values.git.tag }}), please note that it is strongly recommended to avoid using rolling tags in a production environment.
+info https://docs.bitnami.com/containers/how-to/understand-rolling-tags-containers/
{{- end }}
{{- end -}}
bitnami/pytorch/templates/configmap.yaml
+13
View File
@@ -0,0 +1,13 @@
{{- if .Files.Glob "files/*" }}
apiVersion: v1
kind: ConfigMap
metadata:
name: {{ include "pytorch.fullname" . }}-files
labels:
app.kubernetes.io/name: {{ include "pytorch.name" . }}
helm.sh/chart: {{ include "pytorch.chart" . }}
app.kubernetes.io/instance: {{ .Release.Name }}
app.kubernetes.io/managed-by: {{ .Release.Service }}
data:
{{ (.Files.Glob "files/*").AsConfig | indent 2 }}
{{ end }}

Some files were not shown because too many files have changed in this diff Show More