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

[bitnami/*] Use new default branch name in links (#12943)

Browse Source 
* [bitnami/*] Use new default branch name in links

Signed-off-by: Fran Mulero <fmulero@vmware.com>

* Update README.md with readme-generator-for-helm

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>

Signed-off-by: Fran Mulero <fmulero@vmware.com>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
Co-authored-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Fran Mulero
2022-10-17 15:37:01 +02:00
committed by GitHub
co-authored by Bitnami Containers
parent 62c67c1b37
commit a529e02597
252 changed files with 818 additions and 818 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/airflow/Chart.yaml
+1 -1
View File
@@ -18,7 +18,7 @@ dependencies:
version: 2.x.x
description: Apache Airflow is a tool to express and execute workflows as directed acyclic graphs (DAGs). It includes utilities to schedule tasks, monitor task progress and handle task dependencies.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/airflow
home: https://github.com/bitnami/charts/tree/main/bitnami/airflow
icon: https://bitnami.com/assets/stacks/airflow/img/airflow-stack-220x234.png
keywords:
- apache
bitnami/airflow/README.md
+2 -2
View File
@@ -614,7 +614,7 @@ This is useful if you plan on using [Bitnami's sealed secrets](https://github.co
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
### Install extra python packages
@@ -634,7 +634,7 @@ Celery executor is the default value for this chart with it you can scale out th
#### KubernetesExecutor
The kubernetes executor is introduced in Apache Airflow 1.10.0. The Kubernetes executor will create a new pod for every task instance using the `pod_template.yaml` that you can find [templates/config/configmap.yaml](https://github.com/bitnami/charts/blob/master/bitnami/airflow/templates/config/configmap.yaml), otherwise you can override this template using `worker.podTemplate`. To enable `KubernetesExecutor` set the following parameters.
The kubernetes executor is introduced in Apache Airflow 1.10.0. The Kubernetes executor will create a new pod for every task instance using the `pod_template.yaml` that you can find [templates/config/configmap.yaml](https://github.com/bitnami/charts/blob/main/bitnami/airflow/templates/config/configmap.yaml), otherwise you can override this template using `worker.podTemplate`. To enable `KubernetesExecutor` set the following parameters.
> NOTE: Redis&reg; is not needed to be deployed when using KubernetesExecutor so you must disable it using `redis.enabled=false`.
bitnami/airflow/values.yaml
+3 -3
View File
@@ -1440,7 +1440,7 @@ metrics:
##
labels: {}
## @param metrics.serviceMonitor.selector Prometheus instance selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
selector: {}
## @param metrics.serviceMonitor.relabelings RelabelConfigs to apply to samples before scraping
@@ -1459,7 +1459,7 @@ metrics:
## @section Airflow database parameters
## PostgreSQL chart configuration
## ref: https://github.com/bitnami/charts/blob/master/bitnami/postgresql/values.yaml
## ref: https://github.com/bitnami/charts/blob/main/bitnami/postgresql/values.yaml
## @param postgresql.enabled Switch to enable or disable the PostgreSQL helm chart
## @param postgresql.auth.enablePostgresUser Assign a password to the "postgres" admin user. Otherwise, remote access will be blocked for this user
## @param postgresql.auth.username Name for a custom user to create
@@ -1497,7 +1497,7 @@ externalDatabase:
existingSecretPasswordKey: ""
## Redis&reg; chart configuration
## ref: https://github.com/bitnami/charts/blob/master/bitnami/redis/values.yaml
## ref: https://github.com/bitnami/charts/blob/main/bitnami/redis/values.yaml
## @param redis.enabled Switch to enable or disable the Redis&reg; helm
## @param redis.auth.enabled Enable password authentication
## @param redis.auth.password Redis&reg; password
bitnami/apache/Chart.yaml
+1 -1
View File
@@ -10,7 +10,7 @@ dependencies:
version: 2.x.x
description: Apache HTTP Server is an open-source HTTP server. The goal of this project is to provide a secure, efficient and extensible server that provides HTTP services in sync with the current HTTP standards.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/apache
home: https://github.com/bitnami/charts/tree/main/bitnami/apache
icon: https://bitnami.com/assets/stacks/apache/img/apache-stack-220x234.png
keywords:
- apache
bitnami/apache/README.md
+3 -3
View File
@@ -7,7 +7,7 @@ Apache HTTP Server is an open-source HTTP server. The goal of this project is to
[Overview of Apache](https://httpd.apache.org/)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```bash
@@ -287,7 +287,7 @@ Refer to the [chart documentation](https://docs.bitnami.com/kubernetes/infrastru
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod affinity in the [Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use the preset configurations for pod affinity, pod anti-affinity, and node affinity available in the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, you can use the preset configurations for pod affinity, pod anti-affinity, and node affinity available in the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
## Troubleshooting
@@ -297,7 +297,7 @@ Find more information about how to deal with common errors related to Bitnami's
### 7.4.0
This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/master/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/main/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
### 7.0.0
bitnami/apache/templates/NOTES.txt
+1 -1
View File
@@ -40,7 +40,7 @@ APP VERSION: {{ .Chart.AppVersion }}
{{/* WARNINGS */}}
{{- if not (include "apache.useHtdocs" .) }}
WARNING: You did not provide a custom web application. Apache will be deployed with a default page. Check the README section "Deploying your custom web application" in https://github.com/bitnami/charts/blob/master/bitnami/apache/README.md#deploying-a-custom-web-application.
WARNING: You did not provide a custom web application. Apache will be deployed with a default page. Check the README section "Deploying your custom web application" in https://github.com/bitnami/charts/blob/main/bitnami/apache/README.md#deploying-a-custom-web-application.
{{- 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.
bitnami/argo-cd/README.md
+29 -29
View File
@@ -7,7 +7,7 @@ Argo CD is a continuous delivery tool for Kubernetes based on GitOps.
[Overview of Argo CD](https://argoproj.github.io/cd)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -80,7 +80,7 @@ The command removes all the Kubernetes components associated with the chart and
| ------------------- | ------------------------------------------------------------------------------------------------------- | --------------------- |
| `image.registry` | Argo CD image registry | `docker.io` |
| `image.repository` | Argo CD image repository | `bitnami/argo-cd` |
| `image.tag` | Argo CD image tag (immutable tags are recommended) | `2.4.12-debian-11-r0` |
| `image.tag` | Argo CD image tag (immutable tags are recommended) | `2.4.14-debian-11-r0` |
| `image.digest` | Argo CD image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `image.pullPolicy` | Argo CD image pull policy | `IfNotPresent` |
| `image.pullSecrets` | Argo CD image pull secrets | `[]` |
@@ -464,7 +464,7 @@ The command removes all the Kubernetes components associated with the chart and
| ------------------------------------------------------- | --------------------------------------------------------------------------------------------------- | --------------------- |
| `dex.image.registry` | Dex image registry | `docker.io` |
| `dex.image.repository` | Dex image repository | `bitnami/dex` |
| `dex.image.tag` | Dex image tag (immutable tags are recommended) | `2.33.1-debian-11-r0` |
| `dex.image.tag` | Dex image tag (immutable tags are recommended) | `2.35.1-debian-11-r0` |
| `dex.image.digest` | Dex image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `dex.image.pullPolicy` | Dex image pull policy | `IfNotPresent` |
| `dex.image.pullSecrets` | Dex image pull secrets | `[]` |
@@ -604,7 +604,7 @@ The command removes all the Kubernetes components associated with the chart and
| `volumePermissions.enabled` | Enable init container that changes the owner/group of the PV mount point to `runAsUser:fsGroup` | `false` |
| `volumePermissions.image.registry` | Bitnami Shell image registry | `docker.io` |
| `volumePermissions.image.repository` | Bitnami Shell image repository | `bitnami/bitnami-shell` |
| `volumePermissions.image.tag` | Bitnami Shell image tag (immutable tags are recommended) | `11-debian-11-r35` |
| `volumePermissions.image.tag` | Bitnami Shell image tag (immutable tags are recommended) | `11-debian-11-r38` |
| `volumePermissions.image.digest` | Bitnami Shell image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `volumePermissions.image.pullPolicy` | Bitnami Shell image pull policy | `IfNotPresent` |
| `volumePermissions.image.pullSecrets` | Bitnami Shell image pull secrets | `[]` |
@@ -615,30 +615,30 @@ The command removes all the Kubernetes components associated with the chart and
### Other Parameters
| Name | Description | Value |
| ----------------------------------------- | ----------------------------------------------------------------------------------------------------- | --------------------- |
| `rbac.create` | Specifies whether RBAC resources should be created | `true` |
| `redis.image.registry` | Redis image registry | `docker.io` |
| `redis.image.repository` | Redis image repository | `bitnami/redis` |
| `redis.image.tag` | Redis image tag (immutable tags are recommended) | `7.0.4-debian-11-r23` |
| `redis.image.digest` | Redis image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `redis.image.pullPolicy` | Redis image pull policy | `IfNotPresent` |
| `redis.image.pullSecrets` | Redis image pull secrets | `[]` |
| `redis.enabled` | Enable Redis dependency | `true` |
| `redis.nameOverride` | Name override for the Redis dependency | `""` |
| `redis.service.port` | Service port for Redis dependency | `6379` |
| `redis.auth.enabled` | Enable Redis dependency authentication | `true` |
| `redis.auth.existingSecret` | Existing secret to load redis dependency password | `""` |
| `redis.auth.existingSecretPasswordKey` | Pasword key name inside the existing secret | `redis-password` |
| `redis.architecture` | Redis&reg; architecture. Allowed values: `standalone` or `replication` | `standalone` |
| `externalRedis.host` | External Redis host | `""` |
| `externalRedis.port` | External Redis port | `6379` |
| `externalRedis.password` | External Redis password | `""` |
| `externalRedis.existingSecret` | Existing secret for the external redis | `""` |
| `externalRedis.existingSecretPasswordKey` | Password key for the existing secret containing the external redis password | `redis-password` |
| `redisWait.enabled` | Enables waiting for redis | `true` |
| `redisWait.extraArgs` | Additional arguments for the redis-cli call, such as TLS | `""` |
| `redisWait.securityContext` | Security context for init container | `{}` |
| Name | Description | Value |
| ----------------------------------------- | ----------------------------------------------------------------------------------------------------- | -------------------- |
| `rbac.create` | Specifies whether RBAC resources should be created | `true` |
| `redis.image.registry` | Redis image registry | `docker.io` |
| `redis.image.repository` | Redis image repository | `bitnami/redis` |
| `redis.image.tag` | Redis image tag (immutable tags are recommended) | `7.0.5-debian-11-r5` |
| `redis.image.digest` | Redis image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `redis.image.pullPolicy` | Redis image pull policy | `IfNotPresent` |
| `redis.image.pullSecrets` | Redis image pull secrets | `[]` |
| `redis.enabled` | Enable Redis dependency | `true` |
| `redis.nameOverride` | Name override for the Redis dependency | `""` |
| `redis.service.port` | Service port for Redis dependency | `6379` |
| `redis.auth.enabled` | Enable Redis dependency authentication | `true` |
| `redis.auth.existingSecret` | Existing secret to load redis dependency password | `""` |
| `redis.auth.existingSecretPasswordKey` | Pasword key name inside the existing secret | `redis-password` |
| `redis.architecture` | Redis&reg; architecture. Allowed values: `standalone` or `replication` | `standalone` |
| `externalRedis.host` | External Redis host | `""` |
| `externalRedis.port` | External Redis port | `6379` |
| `externalRedis.password` | External Redis password | `""` |
| `externalRedis.existingSecret` | Existing secret for the external redis | `""` |
| `externalRedis.existingSecretPasswordKey` | Password key for the existing secret containing the external redis password | `redis-password` |
| `redisWait.enabled` | Enables waiting for redis | `true` |
| `redisWait.extraArgs` | Additional arguments for the redis-cli call, such as TLS | `""` |
| `redisWait.securityContext` | Security context for init container | `{}` |
The above parameters map to the env variables defined in [bitnami/argo-cd](https://github.com/bitnami/containers/tree/main/bitnami/argo-cd). For more information please refer to the [bitnami/argo-cd](https://github.com/bitnami/containers/tree/main/bitnami/argo-cd) image documentation.
@@ -718,7 +718,7 @@ If additional containers are needed in the same pod as argo-cd (such as addition
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
## Troubleshooting
bitnami/argo-cd/values.yaml
+4 -4
View File
@@ -351,7 +351,7 @@ controller:
##
metricRelabelings: []
## @param controller.metrics.serviceMonitor.selector ServiceMonitor selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
## selector:
## prometheus: my-prometheus
@@ -949,7 +949,7 @@ server:
##
metricRelabelings: []
## @param server.metrics.serviceMonitor.selector ServiceMonitor selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
## selector:
## prometheus: my-prometheus
@@ -1553,7 +1553,7 @@ repoServer:
##
metricRelabelings: []
## @param repoServer.metrics.serviceMonitor.selector ServiceMonitor selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
## selector:
## prometheus: my-prometheus
@@ -2012,7 +2012,7 @@ dex:
##
metricRelabelings: []
## @param dex.metrics.serviceMonitor.selector ServiceMonitor selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
## selector:
## prometheus: my-prometheus
bitnami/argo-workflows/README.md
+5 -5
View File
@@ -82,7 +82,7 @@ The command removes all the Kubernetes components associated with the chart and
| -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | --------------------------- |
| `server.image.registry` | server image registry | `docker.io` |
| `server.image.repository` | server image repository | `bitnami/argo-workflow-cli` |
| `server.image.tag` | server image tag (immutable tags are recommended) | `3.3.9-scratch-r2` |
| `server.image.tag` | server image tag (immutable tags are recommended) | `3.4.1-scratch-r0` |
| `server.image.digest` | server image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `server.image.pullPolicy` | server image pull policy | `Always` |
| `server.image.pullSecrets` | server image pull secrets | `[]` |
@@ -186,7 +186,7 @@ The command removes all the Kubernetes components associated with the chart and
| ------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------- | ---------------------------------- |
| `controller.image.registry` | controller image registry | `docker.io` |
| `controller.image.repository` | controller image repository | `bitnami/argo-workflow-controller` |
| `controller.image.tag` | controller image tag (immutable tags are recommended) | `3.3.9-scratch-r1` |
| `controller.image.tag` | controller image tag (immutable tags are recommended) | `3.4.0-scratch-r0` |
| `controller.image.digest` | controller image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `controller.image.pullPolicy` | controller image pull policy | `IfNotPresent` |
| `controller.image.pullSecrets` | controller image pull secrets | `[]` |
@@ -292,7 +292,7 @@ The command removes all the Kubernetes components associated with the chart and
| ---------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | ---------------------------- |
| `executor.image.registry` | executor image registry | `docker.io` |
| `executor.image.repository` | executor image repository | `bitnami/argo-workflow-exec` |
| `executor.image.tag` | executor image tag (immutable tags are recommended) | `3.3.9-debian-11-r5` |
| `executor.image.tag` | executor image tag (immutable tags are recommended) | `3.4.0-debian-11-r2` |
| `executor.image.digest` | executor image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `executor.image.pullPolicy` | executor image pull policy | `Always` |
| `executor.image.pullSecrets` | executor image pull secrets | `[]` |
@@ -431,7 +431,7 @@ externalDatabase.database=bitnami_wordpress
### Ingress
This chart provides support for Ingress resources. If you have an ingress controller installed on your cluster, such as [nginx-ingress-controller](https://github.com/bitnami/charts/tree/master/bitnami/nginx-ingress-controller) or [contour](https://github.com/bitnami/charts/tree/master/bitnami/contour) you can utilize the ingress controller to serve your application.
This chart provides support for Ingress resources. If you have an ingress controller installed on your cluster, such as [nginx-ingress-controller](https://github.com/bitnami/charts/tree/main/bitnami/nginx-ingress-controller) or [contour](https://github.com/bitnami/charts/tree/main/bitnami/contour) you can utilize the ingress controller to serve your application.
To enable Ingress integration, set `ingress.enabled` to `true`. The `ingress.hostname` property can be used to set the host name. The `ingress.tls` parameter can be used to add the TLS configuration for this host. It is also possible to have more than one host, with a separate TLS configuration for each host. [Learn more about configuring and using Ingress](https://docs.bitnami.com/kubernetes/infrastructure/argo-workflows//configuration/configure-ingress/).
@@ -460,7 +460,7 @@ If additional containers are needed in the same pod as argo-workflows (such as a
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
## Troubleshooting
bitnami/aspnet-core/Chart.yaml
+1 -1
View File
@@ -10,7 +10,7 @@ dependencies:
version: 2.x.x
description: ASP.NET Core is an open-source framework for web application development created by Microsoft. It runs on both the full .NET Framework, on Windows, and the cross-platform .NET Core.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/aspnet-core
home: https://github.com/bitnami/charts/tree/main/bitnami/aspnet-core
icon: https://bitnami.com/assets/stacks/aspnet-core/img/aspnet-core-stack-220x234.png
keywords:
- asp.net
bitnami/aspnet-core/README.md
+2 -2
View File
@@ -7,7 +7,7 @@ ASP.NET Core is an open-source framework for web application development created
[Overview of ASP.NET](https://github.com/dotnet/aspnetcore)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -396,7 +396,7 @@ extraVolumes:
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
### Ingress
bitnami/cassandra/Chart.yaml
+1 -1
View File
@@ -10,7 +10,7 @@ dependencies:
version: 2.x.x
description: Apache Cassandra is an open source distributed database management system designed to handle large amounts of data across many servers, providing high availability with no single point of failure.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/cassandra
home: https://github.com/bitnami/charts/tree/main/bitnami/cassandra
icon: https://bitnami.com/assets/stacks/cassandra/img/cassandra-stack-220x234.png
keywords:
- cassandra
bitnami/cassandra/README.md
+3 -3
View File
@@ -7,7 +7,7 @@ Apache Cassandra is an open source distributed database management system design
[Overview of Apache Cassandra](http://cassandra.apache.org/)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -355,7 +355,7 @@ Refer to the chart documentation for more [information on customizing an Apache
This chart allows you to set custom pod affinity using the `XXX.affinity` parameter(s). Find more information about pod affinity in the [Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.nodeAffinityPreset` parameters.
As an alternative, you can use the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.nodeAffinityPreset` parameters.
## Persistence
@@ -428,7 +428,7 @@ For this version, there have been [intensive efforts](https://cwiki.apache.org/c
- `cluster.replicaCount` is renamed to `replicaCount`.
- `cluster.domain` is renamed to `clusterDomain`.
- Chart labels were adapted to follow the [Helm charts standard labels](https://helm.sh/docs/chart_best_practices/labels/#standard-labels).
- This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/master/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
- This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/main/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
Consequences:
bitnami/cassandra/values.yaml
+10 -10
View File
@@ -748,7 +748,7 @@ metrics:
##
scrapeTimeout: ""
## @param metrics.serviceMonitor.selector Prometheus instance selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
## e.g:
## selector:
## prometheus: my-prometheus
@@ -808,10 +808,10 @@ metrics:
# To get intuition of what is done by cassandra when something is called you can look in cassandra
# https://github.com/apache/cassandra/tree/trunk/src/java/org/apache/cassandra/metrics
# Please avoid to scrape frequently those calls that are iterating over all sstables
# Unaccessible metrics (not enough privilege)
- java:lang:memorypool:.*usagethreshold.*
# Leaf attributes not interesting for us but that are presents in many path
- .*:999thpercentile
- .*:95thpercentile
@@ -823,30 +823,30 @@ metrics:
- .*:meanrate
- .*:mean
- .*:min
# Path present in many metrics but uninterresting
- .*:viewlockacquiretime:.*
- .*:viewreadtime:.*
- .*:cas[a-z]+latency:.*
- .*:colupdatetimedeltahistogram:.*
# Mostly for RPC, do not scrap them
- org:apache:cassandra:db:.*
# columnfamily is an alias for Table metrics
# https://github.com/apache/cassandra/blob/8b3a60b9a7dbefeecc06bace617279612ec7092d/src/java/org/apache/cassandra/metrics/TableMetrics.java#L162
- org:apache:cassandra:metrics:columnfamily:.*
# Should we export metrics for system keyspaces/tables ?
- org:apache:cassandra:metrics:[^:]+:system[^:]*:.*
# Don't scrap us
- com:criteo:nosql:cassandra:exporter:.*
maxScrapFrequencyInSec:
50:
- .*
# Refresh those metrics only every hour as it is costly for cassandra to retrieve them
3600:
- .*:snapshotssize:.*
bitnami/cert-manager/README.md
+54 -54
View File
@@ -7,7 +7,7 @@ Cert Manager is a Kubernetes add-on to automate the management and issuance of T
[Overview of Cert Manager](https://github.com/jetstack/cert-manager)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -85,14 +85,14 @@ The command removes all the Kubernetes components associated with the chart and
| `controller.replicaCount` | Number of Controller replicas | `1` |
| `controller.image.registry` | Controller image registry | `docker.io` |
| `controller.image.repository` | Controller image repository | `bitnami/cert-manager` |
| `controller.image.tag` | Controller image tag (immutable tags are recommended) | `1.9.1-debian-11-r6` |
| `controller.image.tag` | Controller image tag (immutable tags are recommended) | `1.9.1-debian-11-r26` |
| `controller.image.digest` | Controller image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `controller.image.pullPolicy` | Controller image pull policy | `IfNotPresent` |
| `controller.image.pullSecrets` | Controller image pull secrets | `[]` |
| `controller.image.debug` | Controller image debug mode | `false` |
| `controller.acmesolver.image.registry` | Controller image registry | `docker.io` |
| `controller.acmesolver.image.repository` | Controller image repository | `bitnami/acmesolver` |
| `controller.acmesolver.image.tag` | Controller image tag (immutable tags are recommended) | `1.9.1-debian-11-r8` |
| `controller.acmesolver.image.tag` | Controller image tag (immutable tags are recommended) | `1.9.1-debian-11-r28` |
| `controller.acmesolver.image.digest` | Controller image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `controller.acmesolver.image.pullPolicy` | Controller image pull policy | `IfNotPresent` |
| `controller.acmesolver.image.pullSecrets` | Controller image pull secrets | `[]` |
@@ -148,7 +148,7 @@ The command removes all the Kubernetes components associated with the chart and
| `webhook.replicaCount` | Number of Webhook replicas | `1` |
| `webhook.image.registry` | Webhook image registry | `docker.io` |
| `webhook.image.repository` | Webhook image repository | `bitnami/cert-manager-webhook` |
| `webhook.image.tag` | Webhook image tag (immutable tags are recommended) | `1.9.1-debian-11-r5` |
| `webhook.image.tag` | Webhook image tag (immutable tags are recommended) | `1.9.1-debian-11-r24` |
| `webhook.image.digest` | Webhook image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `webhook.image.pullPolicy` | Webhook image pull policy | `IfNotPresent` |
| `webhook.image.pullSecrets` | Webhook image pull secrets | `[]` |
@@ -215,55 +215,55 @@ The command removes all the Kubernetes components associated with the chart and
### CAInjector deployment parameters
| Name | Description | Value |
| -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | -------------------- |
| `cainjector.replicaCount` | Number of CAInjector replicas | `1` |
| `cainjector.image.registry` | CAInjector image registry | `docker.io` |
| `cainjector.image.repository` | CAInjector image repository | `bitnami/cainjector` |
| `cainjector.image.tag` | CAInjector image tag (immutable tags are recommended) | `1.9.1-debian-11-r6` |
| `cainjector.image.digest` | CAInjector image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `cainjector.image.pullPolicy` | CAInjector image pull policy | `IfNotPresent` |
| `cainjector.image.pullSecrets` | CAInjector image pull secrets | `[]` |
| `cainjector.image.debug` | CAInjector image debug mode | `false` |
| `cainjector.resources.limits` | The resources limits for the CAInjector container | `{}` |
| `cainjector.resources.requests` | The requested resources for the CAInjector container | `{}` |
| `cainjector.podSecurityContext.enabled` | Enabled CAInjector pods' Security Context | `true` |
| `cainjector.podSecurityContext.fsGroup` | Set CAInjector pod's Security Context fsGroup | `1001` |
| `cainjector.containerSecurityContext.enabled` | Enabled CAInjector containers' Security Context | `true` |
| `cainjector.containerSecurityContext.runAsUser` | Set CAInjector container's Security Context runAsUser | `1001` |
| `cainjector.containerSecurityContext.runAsNonRoot` | Set CAInjector container's Security Context runAsNonRoot | `true` |
| `cainjector.podAffinityPreset` | Pod affinity preset. Ignored if `cainjector.affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `cainjector.podAntiAffinityPreset` | Pod anti-affinity preset. Ignored if `cainjector.affinity` is set. Allowed values: `soft` or `hard` | `soft` |
| `cainjector.nodeAffinityPreset.type` | Node affinity preset type. Ignored if `cainjector.affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `cainjector.nodeAffinityPreset.key` | Node label key to match. Ignored if `cainjector.affinity` is set | `""` |
| `cainjector.nodeAffinityPreset.values` | Node label values to match. Ignored if `cainjector.affinity` is set | `[]` |
| `cainjector.affinity` | Affinity for Cert Manager CAInjector | `{}` |
| `cainjector.nodeSelector` | Node labels for pod assignment | `{}` |
| `cainjector.command` | Override CAInjector default command | `[]` |
| `cainjector.args` | Override CAInjector default args | `[]` |
| `cainjector.priorityClassName` | CAInjector pod priority class name | `""` |
| `cainjector.runtimeClassName` | Name of the runtime class to be used by pod(s) | `""` |
| `cainjector.schedulerName` | Name of the k8s scheduler (other than default) | `""` |
| `cainjector.topologySpreadConstraints` | Topology Spread Constraints for pod assignment | `[]` |
| `cainjector.hostAliases` | Custom host aliases for CAInjector pods | `[]` |
| `cainjector.tolerations` | Tolerations for pod assignment | `[]` |
| `cainjector.podLabels` | Extra labels for CAInjector pods | `{}` |
| `cainjector.podAnnotations` | Annotations for CAInjector pods | `{}` |
| `cainjector.lifecycleHooks` | Add lifecycle hooks to the CAInjector deployment | `{}` |
| `cainjector.updateStrategy.type` | Controller deployment update strategy | `RollingUpdate` |
| `cainjector.updateStrategy.rollingUpdate` | Controller deployment rolling update configuration parameters | `{}` |
| `cainjector.extraArgs` | Extra arguments to pass to the CAInjector container | `[]` |
| `cainjector.extraEnvVars` | Add extra environment variables to the CAInjector container | `[]` |
| `cainjector.extraEnvVarsCM` | Name of existing ConfigMap containing extra env vars | `""` |
| `cainjector.extraEnvVarsSecret` | Name of existing Secret containing extra env vars | `""` |
| `cainjector.extraVolumes` | Optionally specify extra list of additional volumes for CAInjector pods | `[]` |
| `cainjector.extraVolumeMounts` | Optionally specify extra list of additional volumeMounts for CAInjector container(s) | `[]` |
| `cainjector.initContainers` | Add additional init containers to the CAInjector pods | `[]` |
| `cainjector.sidecars` | Add additional sidecar containers to the CAInjector pod | `[]` |
| `cainjector.serviceAccount.create` | Specifies whether a ServiceAccount should be created | `true` |
| `cainjector.serviceAccount.name` | The name of the ServiceAccount to use. | `""` |
| `cainjector.serviceAccount.annotations` | Additional custom annotations for the ServiceAccount | `{}` |
| `cainjector.serviceAccount.automountServiceAccountToken` | Automount service account token for the server service account | `true` |
| Name | Description | Value |
| -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | --------------------- |
| `cainjector.replicaCount` | Number of CAInjector replicas | `1` |
| `cainjector.image.registry` | CAInjector image registry | `docker.io` |
| `cainjector.image.repository` | CAInjector image repository | `bitnami/cainjector` |
| `cainjector.image.tag` | CAInjector image tag (immutable tags are recommended) | `1.9.1-debian-11-r26` |
| `cainjector.image.digest` | CAInjector image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `cainjector.image.pullPolicy` | CAInjector image pull policy | `IfNotPresent` |
| `cainjector.image.pullSecrets` | CAInjector image pull secrets | `[]` |
| `cainjector.image.debug` | CAInjector image debug mode | `false` |
| `cainjector.resources.limits` | The resources limits for the CAInjector container | `{}` |
| `cainjector.resources.requests` | The requested resources for the CAInjector container | `{}` |
| `cainjector.podSecurityContext.enabled` | Enabled CAInjector pods' Security Context | `true` |
| `cainjector.podSecurityContext.fsGroup` | Set CAInjector pod's Security Context fsGroup | `1001` |
| `cainjector.containerSecurityContext.enabled` | Enabled CAInjector containers' Security Context | `true` |
| `cainjector.containerSecurityContext.runAsUser` | Set CAInjector container's Security Context runAsUser | `1001` |
| `cainjector.containerSecurityContext.runAsNonRoot` | Set CAInjector container's Security Context runAsNonRoot | `true` |
| `cainjector.podAffinityPreset` | Pod affinity preset. Ignored if `cainjector.affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `cainjector.podAntiAffinityPreset` | Pod anti-affinity preset. Ignored if `cainjector.affinity` is set. Allowed values: `soft` or `hard` | `soft` |
| `cainjector.nodeAffinityPreset.type` | Node affinity preset type. Ignored if `cainjector.affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `cainjector.nodeAffinityPreset.key` | Node label key to match. Ignored if `cainjector.affinity` is set | `""` |
| `cainjector.nodeAffinityPreset.values` | Node label values to match. Ignored if `cainjector.affinity` is set | `[]` |
| `cainjector.affinity` | Affinity for Cert Manager CAInjector | `{}` |
| `cainjector.nodeSelector` | Node labels for pod assignment | `{}` |
| `cainjector.command` | Override CAInjector default command | `[]` |
| `cainjector.args` | Override CAInjector default args | `[]` |
| `cainjector.priorityClassName` | CAInjector pod priority class name | `""` |
| `cainjector.runtimeClassName` | Name of the runtime class to be used by pod(s) | `""` |
| `cainjector.schedulerName` | Name of the k8s scheduler (other than default) | `""` |
| `cainjector.topologySpreadConstraints` | Topology Spread Constraints for pod assignment | `[]` |
| `cainjector.hostAliases` | Custom host aliases for CAInjector pods | `[]` |
| `cainjector.tolerations` | Tolerations for pod assignment | `[]` |
| `cainjector.podLabels` | Extra labels for CAInjector pods | `{}` |
| `cainjector.podAnnotations` | Annotations for CAInjector pods | `{}` |
| `cainjector.lifecycleHooks` | Add lifecycle hooks to the CAInjector deployment | `{}` |
| `cainjector.updateStrategy.type` | Controller deployment update strategy | `RollingUpdate` |
| `cainjector.updateStrategy.rollingUpdate` | Controller deployment rolling update configuration parameters | `{}` |
| `cainjector.extraArgs` | Extra arguments to pass to the CAInjector container | `[]` |
| `cainjector.extraEnvVars` | Add extra environment variables to the CAInjector container | `[]` |
| `cainjector.extraEnvVarsCM` | Name of existing ConfigMap containing extra env vars | `""` |
| `cainjector.extraEnvVarsSecret` | Name of existing Secret containing extra env vars | `""` |
| `cainjector.extraVolumes` | Optionally specify extra list of additional volumes for CAInjector pods | `[]` |
| `cainjector.extraVolumeMounts` | Optionally specify extra list of additional volumeMounts for CAInjector container(s) | `[]` |
| `cainjector.initContainers` | Add additional init containers to the CAInjector pods | `[]` |
| `cainjector.sidecars` | Add additional sidecar containers to the CAInjector pod | `[]` |
| `cainjector.serviceAccount.create` | Specifies whether a ServiceAccount should be created | `true` |
| `cainjector.serviceAccount.name` | The name of the ServiceAccount to use. | `""` |
| `cainjector.serviceAccount.annotations` | Additional custom annotations for the ServiceAccount | `{}` |
| `cainjector.serviceAccount.automountServiceAccountToken` | Automount service account token for the server service account | `true` |
### Metrics Parameters
@@ -363,7 +363,7 @@ There are cases where you may want to deploy extra objects, such a ConfigMap con
This chart allows you to set your custom affinity using the `controller.affinity`, `cainjector.affinity` or `webhook.affinity` parameters. Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can make use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `controller.podAffinityPreset`, `cainjector.podAffinityPreset`, `webhook.podAffinityPreset`, `controller.podAntiAffinityPreset`, `cainjector.podAntiAffinityPreset`, `webhook.podAntiAffinityPreset`, `controller.nodeAffinityPreset`, `cainjector.nodeAffinityPreset` or `webhook.nodeAffinityPreset` parameters.
As an alternative, you can make use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `controller.podAffinityPreset`, `cainjector.podAffinityPreset`, `webhook.podAffinityPreset`, `controller.podAntiAffinityPreset`, `cainjector.podAntiAffinityPreset`, `webhook.podAntiAffinityPreset`, `controller.nodeAffinityPreset`, `cainjector.nodeAffinityPreset` or `webhook.nodeAffinityPreset` parameters.
## Troubleshooting
bitnami/cert-manager/values.yaml
+1 -1
View File
@@ -834,7 +834,7 @@ metrics:
##
metricRelabelings: []
## @param metrics.serviceMonitor.selector ServiceMonitor selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
## selector:
## prometheus: my-prometheus
bitnami/clickhouse/README.md
+2 -2
View File
@@ -7,7 +7,7 @@ ClickHouse is an open-source column-oriented OLAP database management system. Us
[Overview of ClickHouse](https://clickhouse.com/)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -455,7 +455,7 @@ startdbScriptsSecret: start-scripts-secret
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
## Troubleshooting
bitnami/clickhouse/values.yaml
+1 -1
View File
@@ -944,7 +944,7 @@ metrics:
##
relabelings: []
## @param metrics.serviceMonitor.selector Prometheus instance selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
## selector:
## prometheus: my-prometheus
##
bitnami/common/Chart.yaml
+1 -1
View File
@@ -4,7 +4,7 @@ apiVersion: v2
# Please make sure that version and appVersion are always the same.
appVersion: 2.0.3
description: A Library Helm Chart for grouping common logic between bitnami charts. This chart is not deployable by itself.
home: https://github.com/bitnami/charts/tree/master/bitnami/common
home: https://github.com/bitnami/charts/tree/main/bitnami/common
icon: https://bitnami.com/downloads/logos/bitnami-mark.png
keywords:
- common
bitnami/common/templates/_secrets.tpl
+2 -2
View File
@@ -8,7 +8,7 @@ Usage:
Params:
- existingSecret - ExistingSecret/String - Optional. The path to the existing secrets in the values.yaml given by the user
to be used instead of the default one. Allows for it to be of type String (just the secret name) for backwards compatibility.
+info: https://github.com/bitnami/charts/tree/master/bitnami/common#existingsecret
+info: https://github.com/bitnami/charts/tree/main/bitnami/common#existingsecret
- defaultNameSuffix - String - Optional. It is used only if we have several secrets in the same deployment.
- context - Dict - Required. The context for the template evaluation.
*/}}
@@ -41,7 +41,7 @@ Usage:
Params:
- existingSecret - ExistingSecret/String - Optional. The path to the existing secrets in the values.yaml given by the user
to be used instead of the default one. Allows for it to be of type String (just the secret name) for backwards compatibility.
+info: https://github.com/bitnami/charts/tree/master/bitnami/common#existingsecret
+info: https://github.com/bitnami/charts/tree/main/bitnami/common#existingsecret
- key - String - Required. Name of the key in the secret.
*/}}
{{- define "common.secrets.key" -}}
bitnami/concourse/README.md
+4 -4
View File
@@ -7,7 +7,7 @@ Concourse is an automation system written in Go. It is most commonly used for CI
[Overview of Concourse](https://concourse-ci.org/)
## TL;DR
```console
@@ -19,7 +19,7 @@ $ helm install my-release my-repo/concourse
This chart bootstraps a [Concourse](https://concourse-ci.org/) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
It also packages [Bitnami Postgresql](https://github.com/bitnami/charts/tree/master/bitnami/postgresql)
It also packages [Bitnami Postgresql](https://github.com/bitnami/charts/tree/main/bitnami/postgresql)
Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
@@ -438,7 +438,7 @@ Refer to the [chart documentation on using an external database](https://docs.bi
### Configure Ingress
This chart provides support for Ingress resources. If you have an Ingress controller installed on your cluster, such as [nginx-ingress-controller](https://github.com/bitnami/charts/tree/master/bitnami/nginx-ingress-controller) or [contour](https://github.com/bitnami/charts/tree/master/bitnami/contour) you can utilize the ingress controller to serve your application.
This chart provides support for Ingress resources. If you have an Ingress controller installed on your cluster, such as [nginx-ingress-controller](https://github.com/bitnami/charts/tree/main/bitnami/nginx-ingress-controller) or [contour](https://github.com/bitnami/charts/tree/main/bitnami/contour) you can utilize the ingress controller to serve your application.
To enable Ingress integration, set `ingress.enabled` to `true`. The `ingress.hostname` property can be used to set the host name. The `ingress.tls` parameter can be used to add the TLS configuration for this host. It is also possible to have more than one host, with a separate TLS configuration for each host. [Learn more about configuring and using Ingress](https://docs.bitnami.com/kubernetes/infrastructure/concourse/configuration/configure-ingress/).
@@ -472,7 +472,7 @@ If additional containers are needed in the same pod as Concourse (such as additi
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod affinity in the [Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
## Troubleshooting
bitnami/concourse/values.yaml
+1 -1
View File
@@ -1235,7 +1235,7 @@ volumePermissions:
## @section Concourse database parameters
## PostgreSQL chart configuration
## ref: https://github.com/bitnami/charts/blob/master/bitnami/postgresql/values.yaml
## ref: https://github.com/bitnami/charts/blob/main/bitnami/postgresql/values.yaml
## @param postgresql.enabled Switch to enable or disable the PostgreSQL helm chart
## @param postgresql.auth.enablePostgresUser Assign a password to the "postgres" admin user. Otherwise, remote access will be blocked for this user
## @param postgresql.auth.username Name for a custom user to create
bitnami/consul/Chart.yaml
+1 -1
View File
@@ -10,7 +10,7 @@ dependencies:
version: 2.x.x
description: HashiCorp Consul is a tool for discovering and configuring services in your infrastructure.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/consul
home: https://github.com/bitnami/charts/tree/main/bitnami/consul
icon: https://bitnami.com/assets/stacks/consul/img/consul-stack-220x234.png
keywords:
- discovering
bitnami/consul/README.md
+2 -2
View File
@@ -387,7 +387,7 @@ Alternatively, you can use a ConfigMap or a Secret with the environment variable
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
### Sidecars and Init Containers
@@ -477,7 +477,7 @@ Affected values:
- `updateStrategy.type` is renamed to `updateStrategy`.
- `configmap` is renamed to `configuration`.
- Chart labels were adapted to follow the [Helm charts standard labels](https://helm.sh/docs/chart_best_practices/labels/#standard-labels).
- This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/master/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
- This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/main/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
### To 7.0.0
bitnami/consul/values.yaml
+1 -1
View File
@@ -756,7 +756,7 @@ metrics:
##
jobLabel: ""
## @param metrics.serviceMonitor.selector ServiceMonitor selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
## selector:
## prometheus: my-prometheus
bitnami/contour-operator/README.md
+5 -5
View File
@@ -7,7 +7,7 @@ The Contour Operator extends the Kubernetes API to create, configure and manage
[Overview of Contour Operator](https://github.com/projectcontour/contour-operator)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -155,18 +155,18 @@ This solution allows to easily deploy multiple Contour instances compared to the
| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | -------------------------- |
| `image.registry` | Contour Operator image registry | `docker.io` |
| `image.repository` | Contour Operator image repository | `bitnami/contour-operator` |
| `image.tag` | Contour Operator image tag (immutable tags are recommended) | `1.22.0-scratch-r2` |
| `image.tag` | Contour Operator image tag (immutable tags are recommended) | `1.22.1-scratch-r2` |
| `image.digest` | Contour Operator image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `image.pullPolicy` | Contour Operator image pull policy | `IfNotPresent` |
| `image.pullSecrets` | Contour Operator image pull secrets | `[]` |
| `contourImage.registry` | Contour Image registry | `docker.io` |
| `contourImage.repository` | Contour Image repository | `bitnami/contour` |
| `contourImage.tag` | Contour Image tag (immutable tags are recommended) | `1.22.0-debian-11-r3` |
| `contourImage.tag` | Contour Image tag (immutable tags are recommended) | `1.22.1-debian-11-r10` |
| `contourImage.digest` | Contour image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `contourImage.pullSecrets` | Contour Image pull secrets | `[]` |
| `envoyImage.registry` | Envoy Image registry | `docker.io` |
| `envoyImage.repository` | Envoy Image repository | `bitnami/envoy` |
| `envoyImage.tag` | Envoy Image tag (immutable tags are recommended) | `1.23.0-debian-11-r7` |
| `envoyImage.tag` | Envoy Image tag (immutable tags are recommended) | `1.23.1-debian-11-r12` |
| `envoyImage.digest` | Envoy image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `envoyImage.pullSecrets` | Envoy Image pull secrets | `[]` |
| `replicaCount` | Number of Contour Operator replicas to deploy | `1` |
@@ -343,7 +343,7 @@ If additional containers are needed in the same pod as contour-operator (such as
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
### Deploying extra resources
bitnami/contour-operator/values.yaml
+1 -1
View File
@@ -440,6 +440,6 @@ metrics:
##
relabelings: []
## @param metrics.serviceMonitor.selector Prometheus instance selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
selector: []
bitnami/contour/Chart.yaml
+1 -1
View File
@@ -10,7 +10,7 @@ dependencies:
version: 2.x.x
description: Contour is an open source Kubernetes ingress controller that works by deploying the Envoy proxy as a reverse proxy and load balancer.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/contour
home: https://github.com/bitnami/charts/tree/main/bitnami/contour
icon: https://bitnami.com/assets/stacks/contour/img/contour-stack-220x234.png
keywords:
- ingress
bitnami/contour/README.md
+214 -214
View File
@@ -7,7 +7,7 @@ Contour is an open source Kubernetes ingress controller that works by deploying
[Overview of Contour](https://github.com/projectcontour/contour)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -27,7 +27,7 @@ Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment
- Kubernetes 1.19+
- Helm 3.2.0+
- An Operator for `ServiceType: LoadBalancer` like [MetalLB](https://github.com/bitnami/charts/tree/master/bitnami/metallb)
- An Operator for `ServiceType: LoadBalancer` like [MetalLB](https://github.com/bitnami/charts/tree/main/bitnami/metallb)
## Installing the Chart
@@ -85,219 +85,219 @@ $ helm uninstall my-release
### Contour parameters
| Name | Description | Value |
| ------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | --------------------- |
| `existingConfigMap` | Specifies the name of an externally-defined ConfigMap to use as the configuration (this is mutually exclusive with `configInline`) | `""` |
| `configInline` | Specifies Contour's configuration directly in YAML format | `{}` |
| `contour.enabled` | Contour Deployment creation. | `true` |
| `contour.image.registry` | Contour image registry | `docker.io` |
| `contour.image.repository` | Contour image name | `bitnami/contour` |
| `contour.image.tag` | Contour image tag | `1.22.0-debian-11-r4` |
| `contour.image.digest` | Contour image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `contour.image.pullPolicy` | Contour Image pull policy | `IfNotPresent` |
| `contour.image.pullSecrets` | Contour Image pull secrets | `[]` |
| `contour.image.debug` | Enable image debug mode | `false` |
| `contour.replicaCount` | Number of Contour Pod replicas | `1` |
| `contour.priorityClassName` | Priority class assigned to the pods | `""` |
| `contour.schedulerName` | Name of the k8s scheduler (other than default) | `""` |
| `contour.terminationGracePeriodSeconds` | In seconds, time the given to the Contour pod needs to terminate gracefully | `""` |
| `contour.topologySpreadConstraints` | Topology Spread Constraints for pod assignment | `[]` |
| `contour.containerPorts.xds` | Set xds port inside Contour pod | `8001` |
| `contour.containerPorts.metrics` | Set metrics port inside Contour pod | `8000` |
| `contour.hostAliases` | Add deployment host aliases | `[]` |
| `contour.updateStrategy` | Strategy to use to update Pods | `{}` |
| `contour.extraArgs` | Extra arguments passed to Contour container | `[]` |
| `contour.resources.limits` | Specify resource limits which the container is not allowed to succeed. | `{}` |
| `contour.resources.requests` | Specify resource requests which the container needs to spawn. | `{}` |
| `contour.manageCRDs` | Manage the creation, upgrade and deletion of Contour CRDs. | `true` |
| `contour.podAffinityPreset` | Contour Pod affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `contour.podAntiAffinityPreset` | Contour Pod anti-affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `soft` |
| `contour.podLabels` | Extra labels for Contour pods | `{}` |
| `contour.lifecycleHooks` | lifecycleHooks for the container to automate configuration before or after startup. | `{}` |
| `contour.customLivenessProbe` | Override default liveness probe | `{}` |
| `contour.customReadinessProbe` | Override default readiness probe | `{}` |
| `contour.customStartupProbe` | Override default startup probe | `{}` |
| `contour.nodeAffinityPreset.type` | Contour Node affinity preset type. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `contour.nodeAffinityPreset.key` | Contour Node label key to match Ignored if `affinity` is set. | `""` |
| `contour.nodeAffinityPreset.values` | Contour Node label values to match. Ignored if `affinity` is set. | `[]` |
| `contour.command` | Override default command | `[]` |
| `contour.args` | Override default args | `[]` |
| `contour.affinity` | Affinity for Contour pod assignment | `{}` |
| `contour.nodeSelector` | Node labels for Contour pod assignment | `{}` |
| `contour.tolerations` | Tolerations for Contour pod assignment | `[]` |
| `contour.podAnnotations` | Contour Pod annotations | `{}` |
| `contour.serviceAccount.create` | Create a serviceAccount for the Contour pod | `true` |
| `contour.serviceAccount.name` | Use the serviceAccount with the specified name, a name is generated using the fullname template | `""` |
| `contour.serviceAccount.automountServiceAccountToken` | Automount service account token for the server service account | `true` |
| `contour.serviceAccount.annotations` | Annotations for service account. Evaluated as a template. Only used if `create` is `true`. | `{}` |
| `contour.podSecurityContext.enabled` | Default backend Pod securityContext | `true` |
| `contour.podSecurityContext.fsGroup` | Set Default backend Pod's Security Context fsGroup | `1001` |
| `contour.containerSecurityContext.enabled` | Envoy Container securityContext | `true` |
| `contour.containerSecurityContext.runAsUser` | User ID for the Contour container (to change this, http and https containerPorts must be set to >1024) | `1001` |
| `contour.containerSecurityContext.runAsNonRoot` | Run as non root | `true` |
| `contour.livenessProbe.enabled` | Enable/disable the Liveness probe | `true` |
| `contour.livenessProbe.initialDelaySeconds` | Delay before liveness probe is initiated | `120` |
| `contour.livenessProbe.periodSeconds` | How often to perform the probe | `20` |
| `contour.livenessProbe.timeoutSeconds` | When the probe times out | `5` |
| `contour.livenessProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded. | `6` |
| `contour.livenessProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed. | `1` |
| `contour.readinessProbe.enabled` | Enable/disable the readiness probe | `true` |
| `contour.readinessProbe.initialDelaySeconds` | Delay before readiness probe is initiated | `15` |
| `contour.readinessProbe.periodSeconds` | How often to perform the probe | `10` |
| `contour.readinessProbe.timeoutSeconds` | When the probe times out | `5` |
| `contour.readinessProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded. | `3` |
| `contour.readinessProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed. | `1` |
| `contour.startupProbe.enabled` | Enable/disable the startup probe | `false` |
| `contour.startupProbe.initialDelaySeconds` | Delay before startup probe is initiated | `15` |
| `contour.startupProbe.periodSeconds` | How often to perform the probe | `10` |
| `contour.startupProbe.timeoutSeconds` | When the probe times out | `5` |
| `contour.startupProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded. | `3` |
| `contour.startupProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed. | `1` |
| `contour.certgen.serviceAccount.create` | Create a serviceAccount for the Contour pod | `true` |
| `contour.certgen.serviceAccount.name` | Use the serviceAccount with the specified name, a name is generated using the fullname template | `""` |
| `contour.certgen.serviceAccount.automountServiceAccountToken` | Automount service account token for the server service account | `true` |
| `contour.certgen.serviceAccount.annotations` | Annotations for service account. Evaluated as a template. Only used if `create` is `true`. | `{}` |
| `contour.certgen.certificateLifetime` | Generated certificate lifetime (in days). | `365` |
| `contour.tlsExistingSecret` | Name of the existingSecret to be use in Contour deployment. If it is not nil `contour.certgen` will be disabled. | `""` |
| `contour.service.type` | Service type | `ClusterIP` |
| `contour.service.ports.xds` | Contour service xds port | `8001` |
| `contour.service.ports.metrics` | Contour service xds port | `8000` |
| `contour.service.nodePorts.xds` | Node port for HTTP | `""` |
| `contour.service.clusterIP` | Contour service Cluster IP | `""` |
| `contour.service.loadBalancerIP` | Contour service Load Balancer IP | `""` |
| `contour.service.loadBalancerSourceRanges` | Contour service Load Balancer sources | `[]` |
| `contour.service.externalTrafficPolicy` | Contour service external traffic policy | `Cluster` |
| `contour.service.annotations` | Additional custom annotations for Contour service | `{}` |
| `contour.service.extraPorts` | Extra port to expose on Contour service | `[]` |
| `contour.service.sessionAffinity` | Session Affinity for Kubernetes service, can be "None" or "ClientIP" | `None` |
| `contour.service.sessionAffinityConfig` | Additional settings for the sessionAffinity | `{}` |
| `contour.initContainers` | Attach additional init containers to Contour pods | `[]` |
| `contour.sidecars` | Add additional sidecar containers to the Contour pods | `[]` |
| `contour.extraVolumes` | Array to add extra volumes | `[]` |
| `contour.extraVolumeMounts` | Array to add extra mounts (normally used with extraVolumes) | `[]` |
| `contour.extraEnvVars` | Array containing extra env vars to be added to all Contour containers | `[]` |
| `contour.extraEnvVarsCM` | ConfigMap containing extra env vars to be added to all Contour containers | `""` |
| `contour.extraEnvVarsSecret` | Secret containing extra env vars to be added to all Contour containers | `""` |
| `contour.ingressClass.name` | Name of the ingress class to route through this controller. | `""` |
| `contour.ingressClass.create` | Whether to create or not the IngressClass resource | `true` |
| `contour.ingressClass.default` | Mark IngressClass resource as default for cluster | `true` |
| `contour.debug` | Enable Contour debug log level | `false` |
| `contour.kubernetesDebug` | Contour kubernetes debug log level, Default 0, minimum 0, maximum 9. | `0` |
| `contour.rootNamespaces` | Restrict Contour to searching these namespaces for root ingress routes. | `""` |
| Name | Description | Value |
| ------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | ---------------------- |
| `existingConfigMap` | Specifies the name of an externally-defined ConfigMap to use as the configuration (this is mutually exclusive with `configInline`) | `""` |
| `configInline` | Specifies Contour's configuration directly in YAML format | `{}` |
| `contour.enabled` | Contour Deployment creation. | `true` |
| `contour.image.registry` | Contour image registry | `docker.io` |
| `contour.image.repository` | Contour image name | `bitnami/contour` |
| `contour.image.tag` | Contour image tag | `1.22.1-debian-11-r11` |
| `contour.image.digest` | Contour image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `contour.image.pullPolicy` | Contour Image pull policy | `IfNotPresent` |
| `contour.image.pullSecrets` | Contour Image pull secrets | `[]` |
| `contour.image.debug` | Enable image debug mode | `false` |
| `contour.replicaCount` | Number of Contour Pod replicas | `1` |
| `contour.priorityClassName` | Priority class assigned to the pods | `""` |
| `contour.schedulerName` | Name of the k8s scheduler (other than default) | `""` |
| `contour.terminationGracePeriodSeconds` | In seconds, time the given to the Contour pod needs to terminate gracefully | `""` |
| `contour.topologySpreadConstraints` | Topology Spread Constraints for pod assignment | `[]` |
| `contour.containerPorts.xds` | Set xds port inside Contour pod | `8001` |
| `contour.containerPorts.metrics` | Set metrics port inside Contour pod | `8000` |
| `contour.hostAliases` | Add deployment host aliases | `[]` |
| `contour.updateStrategy` | Strategy to use to update Pods | `{}` |
| `contour.extraArgs` | Extra arguments passed to Contour container | `[]` |
| `contour.resources.limits` | Specify resource limits which the container is not allowed to succeed. | `{}` |
| `contour.resources.requests` | Specify resource requests which the container needs to spawn. | `{}` |
| `contour.manageCRDs` | Manage the creation, upgrade and deletion of Contour CRDs. | `true` |
| `contour.podAffinityPreset` | Contour Pod affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `contour.podAntiAffinityPreset` | Contour Pod anti-affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `soft` |
| `contour.podLabels` | Extra labels for Contour pods | `{}` |
| `contour.lifecycleHooks` | lifecycleHooks for the container to automate configuration before or after startup. | `{}` |
| `contour.customLivenessProbe` | Override default liveness probe | `{}` |
| `contour.customReadinessProbe` | Override default readiness probe | `{}` |
| `contour.customStartupProbe` | Override default startup probe | `{}` |
| `contour.nodeAffinityPreset.type` | Contour Node affinity preset type. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `contour.nodeAffinityPreset.key` | Contour Node label key to match Ignored if `affinity` is set. | `""` |
| `contour.nodeAffinityPreset.values` | Contour Node label values to match. Ignored if `affinity` is set. | `[]` |
| `contour.command` | Override default command | `[]` |
| `contour.args` | Override default args | `[]` |
| `contour.affinity` | Affinity for Contour pod assignment | `{}` |
| `contour.nodeSelector` | Node labels for Contour pod assignment | `{}` |
| `contour.tolerations` | Tolerations for Contour pod assignment | `[]` |
| `contour.podAnnotations` | Contour Pod annotations | `{}` |
| `contour.serviceAccount.create` | Create a serviceAccount for the Contour pod | `true` |
| `contour.serviceAccount.name` | Use the serviceAccount with the specified name, a name is generated using the fullname template | `""` |
| `contour.serviceAccount.automountServiceAccountToken` | Automount service account token for the server service account | `true` |
| `contour.serviceAccount.annotations` | Annotations for service account. Evaluated as a template. Only used if `create` is `true`. | `{}` |
| `contour.podSecurityContext.enabled` | Default backend Pod securityContext | `true` |
| `contour.podSecurityContext.fsGroup` | Set Default backend Pod's Security Context fsGroup | `1001` |
| `contour.containerSecurityContext.enabled` | Envoy Container securityContext | `true` |
| `contour.containerSecurityContext.runAsUser` | User ID for the Contour container (to change this, http and https containerPorts must be set to >1024) | `1001` |
| `contour.containerSecurityContext.runAsNonRoot` | Run as non root | `true` |
| `contour.livenessProbe.enabled` | Enable/disable the Liveness probe | `true` |
| `contour.livenessProbe.initialDelaySeconds` | Delay before liveness probe is initiated | `120` |
| `contour.livenessProbe.periodSeconds` | How often to perform the probe | `20` |
| `contour.livenessProbe.timeoutSeconds` | When the probe times out | `5` |
| `contour.livenessProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded. | `6` |
| `contour.livenessProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed. | `1` |
| `contour.readinessProbe.enabled` | Enable/disable the readiness probe | `true` |
| `contour.readinessProbe.initialDelaySeconds` | Delay before readiness probe is initiated | `15` |
| `contour.readinessProbe.periodSeconds` | How often to perform the probe | `10` |
| `contour.readinessProbe.timeoutSeconds` | When the probe times out | `5` |
| `contour.readinessProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded. | `3` |
| `contour.readinessProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed. | `1` |
| `contour.startupProbe.enabled` | Enable/disable the startup probe | `false` |
| `contour.startupProbe.initialDelaySeconds` | Delay before startup probe is initiated | `15` |
| `contour.startupProbe.periodSeconds` | How often to perform the probe | `10` |
| `contour.startupProbe.timeoutSeconds` | When the probe times out | `5` |
| `contour.startupProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded. | `3` |
| `contour.startupProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed. | `1` |
| `contour.certgen.serviceAccount.create` | Create a serviceAccount for the Contour pod | `true` |
| `contour.certgen.serviceAccount.name` | Use the serviceAccount with the specified name, a name is generated using the fullname template | `""` |
| `contour.certgen.serviceAccount.automountServiceAccountToken` | Automount service account token for the server service account | `true` |
| `contour.certgen.serviceAccount.annotations` | Annotations for service account. Evaluated as a template. Only used if `create` is `true`. | `{}` |
| `contour.certgen.certificateLifetime` | Generated certificate lifetime (in days). | `365` |
| `contour.tlsExistingSecret` | Name of the existingSecret to be use in Contour deployment. If it is not nil `contour.certgen` will be disabled. | `""` |
| `contour.service.type` | Service type | `ClusterIP` |
| `contour.service.ports.xds` | Contour service xds port | `8001` |
| `contour.service.ports.metrics` | Contour service xds port | `8000` |
| `contour.service.nodePorts.xds` | Node port for HTTP | `""` |
| `contour.service.clusterIP` | Contour service Cluster IP | `""` |
| `contour.service.loadBalancerIP` | Contour service Load Balancer IP | `""` |
| `contour.service.loadBalancerSourceRanges` | Contour service Load Balancer sources | `[]` |
| `contour.service.externalTrafficPolicy` | Contour service external traffic policy | `Cluster` |
| `contour.service.annotations` | Additional custom annotations for Contour service | `{}` |
| `contour.service.extraPorts` | Extra port to expose on Contour service | `[]` |
| `contour.service.sessionAffinity` | Session Affinity for Kubernetes service, can be "None" or "ClientIP" | `None` |
| `contour.service.sessionAffinityConfig` | Additional settings for the sessionAffinity | `{}` |
| `contour.initContainers` | Attach additional init containers to Contour pods | `[]` |
| `contour.sidecars` | Add additional sidecar containers to the Contour pods | `[]` |
| `contour.extraVolumes` | Array to add extra volumes | `[]` |
| `contour.extraVolumeMounts` | Array to add extra mounts (normally used with extraVolumes) | `[]` |
| `contour.extraEnvVars` | Array containing extra env vars to be added to all Contour containers | `[]` |
| `contour.extraEnvVarsCM` | ConfigMap containing extra env vars to be added to all Contour containers | `""` |
| `contour.extraEnvVarsSecret` | Secret containing extra env vars to be added to all Contour containers | `""` |
| `contour.ingressClass.name` | Name of the ingress class to route through this controller. | `""` |
| `contour.ingressClass.create` | Whether to create or not the IngressClass resource | `true` |
| `contour.ingressClass.default` | Mark IngressClass resource as default for cluster | `true` |
| `contour.debug` | Enable Contour debug log level | `false` |
| `contour.kubernetesDebug` | Contour kubernetes debug log level, Default 0, minimum 0, maximum 9. | `0` |
| `contour.rootNamespaces` | Restrict Contour to searching these namespaces for root ingress routes. | `""` |
### Envoy parameters
| Name | Description | Value |
| --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | --------------------- |
| `envoy.enabled` | Envoy Proxy creation | `true` |
| `envoy.image.registry` | Envoy Proxy image registry | `docker.io` |
| `envoy.image.repository` | Envoy Proxy image repository | `bitnami/envoy` |
| `envoy.image.tag` | Envoy Proxy image tag (immutable tags are recommended) | `1.23.0-debian-11-r8` |
| `envoy.image.digest` | Envoy Proxy image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `envoy.image.pullPolicy` | Envoy image pull policy | `IfNotPresent` |
| `envoy.image.pullSecrets` | Envoy image pull secrets | `[]` |
| `envoy.priorityClassName` | Priority class assigned to the pods | `""` |
| `envoy.schedulerName` | Name of the k8s scheduler (other than default) | `""` |
| `envoy.topologySpreadConstraints` | Topology Spread Constraints for pod assignment | `[]` |
| `envoy.extraArgs` | Extra arguments passed to Envoy container | `[]` |
| `envoy.hostAliases` | Add deployment host aliases | `[]` |
| `envoy.resources.limits` | Specify resource limits which the container is not allowed to succeed. | `{}` |
| `envoy.resources.requests` | Specify resource requests which the container needs to spawn. | `{}` |
| `envoy.command` | Override default command | `[]` |
| `envoy.args` | Override default args | `[]` |
| `envoy.shutdownManager.enabled` | Contour shutdownManager sidecar | `true` |
| `envoy.shutdownManager.resources.limits` | Specify resource limits which the container is not allowed to succeed. | `{}` |
| `envoy.shutdownManager.resources.requests` | Specify resource requests which the container needs to spawn. | `{}` |
| `envoy.kind` | Install as deployment or daemonset | `daemonset` |
| `envoy.replicaCount` | Desired number of Controller pods | `1` |
| `envoy.lifecycleHooks` | lifecycleHooks for the container to automate configuration before or after startup. | `{}` |
| `envoy.updateStrategy` | Strategy to use to update Pods | `{}` |
| `envoy.minReadySeconds` | The minimum number of seconds for which a newly created Pod should be ready | `0` |
| `envoy.revisionHistoryLimit` | The number of old history to retain to allow rollback | `10` |
| `envoy.autoscaling.enabled` | Enable autoscaling for Controller | `false` |
| `envoy.autoscaling.minReplicas` | Minimum number of Controller replicas | `1` |
| `envoy.autoscaling.maxReplicas` | Maximum number of Controller replicas | `11` |
| `envoy.autoscaling.targetCPU` | Target CPU utilization percentage | `""` |
| `envoy.autoscaling.targetMemory` | Target Memory utilization percentage | `""` |
| `envoy.podAffinityPreset` | Envoy Pod affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `envoy.podAntiAffinityPreset` | Envoy Pod anti-affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `envoy.nodeAffinityPreset.type` | Envoy Node affinity preset type. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `envoy.nodeAffinityPreset.key` | Envoy Node label key to match Ignored if `affinity` is set. | `""` |
| `envoy.nodeAffinityPreset.values` | Envoy Node label values to match. Ignored if `affinity` is set. | `[]` |
| `envoy.affinity` | Affinity for Envoy pod assignment | `{}` |
| `envoy.nodeSelector` | Node labels for Envoy pod assignment | `{}` |
| `envoy.tolerations` | Tolerations for Envoy pod assignment | `[]` |
| `envoy.podAnnotations` | Envoy Pod annotations | `{}` |
| `envoy.podLabels` | Extra labels for Envoy pods | `{}` |
| `envoy.podSecurityContext.enabled` | Envoy Pod securityContext | `false` |
| `envoy.podSecurityContext.fsGroup` | User ID for the for the mounted volumes | `0` |
| `envoy.podSecurityContext.sysctls` | Array of sysctl options to allow | `[]` |
| `envoy.containerSecurityContext.enabled` | Envoy Container securityContext | `true` |
| `envoy.containerSecurityContext.runAsUser` | User ID for the Envoy container (to change this, http and https containerPorts must be set to >1024) | `1001` |
| `envoy.containerSecurityContext.runAsNonRoot` | Run as non root | `true` |
| `envoy.hostNetwork` | Envoy Pod host network access | `false` |
| `envoy.dnsPolicy` | Envoy Pod Dns Policy's DNS Policy | `ClusterFirst` |
| `envoy.tlsExistingSecret` | Name of the existingSecret to be use in Envoy deployment | `""` |
| `envoy.serviceAccount.create` | Specifies whether a ServiceAccount should be created | `true` |
| `envoy.serviceAccount.name` | The name of the ServiceAccount to use. If not set and create is true, a name is generated using the fullname template | `""` |
| `envoy.serviceAccount.automountServiceAccountToken` | Whether to auto mount API credentials for a service account | `false` |
| `envoy.serviceAccount.annotations` | Annotations for service account. Evaluated as a template. Only used if `create` is `true`. | `{}` |
| `envoy.livenessProbe.enabled` | Enable livenessProbe | `true` |
| `envoy.livenessProbe.initialDelaySeconds` | Initial delay seconds for livenessProbe | `120` |
| `envoy.livenessProbe.periodSeconds` | Period seconds for livenessProbe | `20` |
| `envoy.livenessProbe.timeoutSeconds` | Timeout seconds for livenessProbe | `5` |
| `envoy.livenessProbe.failureThreshold` | Failure threshold for livenessProbe | `6` |
| `envoy.livenessProbe.successThreshold` | Success threshold for livenessProbe | `1` |
| `envoy.readinessProbe.enabled` | Enable/disable the readiness probe | `true` |
| `envoy.readinessProbe.initialDelaySeconds` | Delay before readiness probe is initiated | `10` |
| `envoy.readinessProbe.periodSeconds` | How often to perform the probe | `3` |
| `envoy.readinessProbe.timeoutSeconds` | When the probe times out | `1` |
| `envoy.readinessProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded. | `3` |
| `envoy.readinessProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed. | `1` |
| `envoy.startupProbe.enabled` | Enable/disable the startup probe | `false` |
| `envoy.startupProbe.initialDelaySeconds` | Delay before startup probe is initiated | `15` |
| `envoy.startupProbe.periodSeconds` | How often to perform the probe | `10` |
| `envoy.startupProbe.timeoutSeconds` | When the probe times out | `5` |
| `envoy.startupProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded. | `3` |
| `envoy.startupProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed. | `1` |
| `envoy.customLivenessProbe` | Override default liveness probe | `{}` |
| `envoy.customReadinessProbe` | Override default readiness probe | `{}` |
| `envoy.customStartupProbe` | Override default startup probe | `{}` |
| `envoy.terminationGracePeriodSeconds` | Envoy termination grace period in seconds | `300` |
| `envoy.logLevel` | Envoy log level | `info` |
| `envoy.service.targetPorts` | Map the controller service HTTP/HTTPS port | `{}` |
| `envoy.service.type` | Type of Envoy service to create | `LoadBalancer` |
| `envoy.service.externalTrafficPolicy` | Envoy Service external cluster policy. If `envoy.service.type` is NodePort or LoadBalancer | `Local` |
| `envoy.service.labels` | Labels to add to te envoy service | `{}` |
| `envoy.service.clusterIP` | Internal envoy cluster service IP | `""` |
| `envoy.service.externalIPs` | Envoy service external IP addresses | `[]` |
| `envoy.service.loadBalancerIP` | IP address to assign to load balancer (if supported) | `""` |
| `envoy.service.loadBalancerSourceRanges` | List of IP CIDRs allowed access to load balancer (if supported) | `[]` |
| `envoy.service.ipFamilyPolicy` | , support SingleStack, PreferDualStack and RequireDualStack | `""` |
| `envoy.service.annotations` | Annotations for Envoy service | `{}` |
| `envoy.service.ports.http` | Sets service http port | `80` |
| `envoy.service.ports.https` | Sets service https port | `443` |
| `envoy.service.nodePorts.http` | HTTP Port. If `envoy.service.type` is NodePort and this is non-empty | `""` |
| `envoy.service.nodePorts.https` | HTTPS Port. If `envoy.service.type` is NodePort and this is non-empty | `""` |
| `envoy.service.extraPorts` | Extra ports to expose (normally used with the `sidecar` value) | `[]` |
| `envoy.service.sessionAffinity` | Session Affinity for Kubernetes service, can be "None" or "ClientIP" | `None` |
| `envoy.service.sessionAffinityConfig` | Additional settings for the sessionAffinity | `{}` |
| `envoy.useHostPort` | Enable/disable `hostPort` for TCP/80 and TCP/443 | `true` |
| `envoy.useHostIP` | Enable/disable `hostIP` | `false` |
| `envoy.hostPorts.http` | Sets `hostPort` http port | `80` |
| `envoy.hostPorts.https` | Sets `hostPort` https port | `443` |
| `envoy.hostIPs.http` | Sets `hostIP` http IP | `127.0.0.1` |
| `envoy.hostIPs.https` | Sets `hostIP` https IP | `127.0.0.1` |
| `envoy.containerPorts.http` | Sets http port inside Envoy pod (change this to >1024 to run envoy as a non-root user) | `8080` |
| `envoy.containerPorts.https` | Sets https port inside Envoy pod (change this to >1024 to run envoy as a non-root user) | `8443` |
| `envoy.initContainers` | Attach additional init containers to Envoy pods | `[]` |
| `envoy.sidecars` | Add additional sidecar containers to the Envoy pods | `[]` |
| `envoy.extraVolumes` | Array to add extra volumes | `[]` |
| `envoy.extraVolumeMounts` | Array to add extra mounts (normally used with extraVolumes) | `[]` |
| `envoy.extraEnvVars` | Array containing extra env vars to be added to all Envoy containers | `[]` |
| `envoy.extraEnvVarsCM` | ConfigMap containing extra env vars to be added to all Envoy containers | `""` |
| `envoy.extraEnvVarsSecret` | Secret containing extra env vars to be added to all Envoy containers | `""` |
| Name | Description | Value |
| --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | ---------------------- |
| `envoy.enabled` | Envoy Proxy creation | `true` |
| `envoy.image.registry` | Envoy Proxy image registry | `docker.io` |
| `envoy.image.repository` | Envoy Proxy image repository | `bitnami/envoy` |
| `envoy.image.tag` | Envoy Proxy image tag (immutable tags are recommended) | `1.23.1-debian-11-r14` |
| `envoy.image.digest` | Envoy Proxy image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `envoy.image.pullPolicy` | Envoy image pull policy | `IfNotPresent` |
| `envoy.image.pullSecrets` | Envoy image pull secrets | `[]` |
| `envoy.priorityClassName` | Priority class assigned to the pods | `""` |
| `envoy.schedulerName` | Name of the k8s scheduler (other than default) | `""` |
| `envoy.topologySpreadConstraints` | Topology Spread Constraints for pod assignment | `[]` |
| `envoy.extraArgs` | Extra arguments passed to Envoy container | `[]` |
| `envoy.hostAliases` | Add deployment host aliases | `[]` |
| `envoy.resources.limits` | Specify resource limits which the container is not allowed to succeed. | `{}` |
| `envoy.resources.requests` | Specify resource requests which the container needs to spawn. | `{}` |
| `envoy.command` | Override default command | `[]` |
| `envoy.args` | Override default args | `[]` |
| `envoy.shutdownManager.enabled` | Contour shutdownManager sidecar | `true` |
| `envoy.shutdownManager.resources.limits` | Specify resource limits which the container is not allowed to succeed. | `{}` |
| `envoy.shutdownManager.resources.requests` | Specify resource requests which the container needs to spawn. | `{}` |
| `envoy.kind` | Install as deployment or daemonset | `daemonset` |
| `envoy.replicaCount` | Desired number of Controller pods | `1` |
| `envoy.lifecycleHooks` | lifecycleHooks for the container to automate configuration before or after startup. | `{}` |
| `envoy.updateStrategy` | Strategy to use to update Pods | `{}` |
| `envoy.minReadySeconds` | The minimum number of seconds for which a newly created Pod should be ready | `0` |
| `envoy.revisionHistoryLimit` | The number of old history to retain to allow rollback | `10` |
| `envoy.autoscaling.enabled` | Enable autoscaling for Controller | `false` |
| `envoy.autoscaling.minReplicas` | Minimum number of Controller replicas | `1` |
| `envoy.autoscaling.maxReplicas` | Maximum number of Controller replicas | `11` |
| `envoy.autoscaling.targetCPU` | Target CPU utilization percentage | `""` |
| `envoy.autoscaling.targetMemory` | Target Memory utilization percentage | `""` |
| `envoy.podAffinityPreset` | Envoy Pod affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `envoy.podAntiAffinityPreset` | Envoy Pod anti-affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `envoy.nodeAffinityPreset.type` | Envoy Node affinity preset type. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `envoy.nodeAffinityPreset.key` | Envoy Node label key to match Ignored if `affinity` is set. | `""` |
| `envoy.nodeAffinityPreset.values` | Envoy Node label values to match. Ignored if `affinity` is set. | `[]` |
| `envoy.affinity` | Affinity for Envoy pod assignment | `{}` |
| `envoy.nodeSelector` | Node labels for Envoy pod assignment | `{}` |
| `envoy.tolerations` | Tolerations for Envoy pod assignment | `[]` |
| `envoy.podAnnotations` | Envoy Pod annotations | `{}` |
| `envoy.podLabels` | Extra labels for Envoy pods | `{}` |
| `envoy.podSecurityContext.enabled` | Envoy Pod securityContext | `false` |
| `envoy.podSecurityContext.fsGroup` | User ID for the for the mounted volumes | `0` |
| `envoy.podSecurityContext.sysctls` | Array of sysctl options to allow | `[]` |
| `envoy.containerSecurityContext.enabled` | Envoy Container securityContext | `true` |
| `envoy.containerSecurityContext.runAsUser` | User ID for the Envoy container (to change this, http and https containerPorts must be set to >1024) | `1001` |
| `envoy.containerSecurityContext.runAsNonRoot` | Run as non root | `true` |
| `envoy.hostNetwork` | Envoy Pod host network access | `false` |
| `envoy.dnsPolicy` | Envoy Pod Dns Policy's DNS Policy | `ClusterFirst` |
| `envoy.tlsExistingSecret` | Name of the existingSecret to be use in Envoy deployment | `""` |
| `envoy.serviceAccount.create` | Specifies whether a ServiceAccount should be created | `true` |
| `envoy.serviceAccount.name` | The name of the ServiceAccount to use. If not set and create is true, a name is generated using the fullname template | `""` |
| `envoy.serviceAccount.automountServiceAccountToken` | Whether to auto mount API credentials for a service account | `false` |
| `envoy.serviceAccount.annotations` | Annotations for service account. Evaluated as a template. Only used if `create` is `true`. | `{}` |
| `envoy.livenessProbe.enabled` | Enable livenessProbe | `true` |
| `envoy.livenessProbe.initialDelaySeconds` | Initial delay seconds for livenessProbe | `120` |
| `envoy.livenessProbe.periodSeconds` | Period seconds for livenessProbe | `20` |
| `envoy.livenessProbe.timeoutSeconds` | Timeout seconds for livenessProbe | `5` |
| `envoy.livenessProbe.failureThreshold` | Failure threshold for livenessProbe | `6` |
| `envoy.livenessProbe.successThreshold` | Success threshold for livenessProbe | `1` |
| `envoy.readinessProbe.enabled` | Enable/disable the readiness probe | `true` |
| `envoy.readinessProbe.initialDelaySeconds` | Delay before readiness probe is initiated | `10` |
| `envoy.readinessProbe.periodSeconds` | How often to perform the probe | `3` |
| `envoy.readinessProbe.timeoutSeconds` | When the probe times out | `1` |
| `envoy.readinessProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded. | `3` |
| `envoy.readinessProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed. | `1` |
| `envoy.startupProbe.enabled` | Enable/disable the startup probe | `false` |
| `envoy.startupProbe.initialDelaySeconds` | Delay before startup probe is initiated | `15` |
| `envoy.startupProbe.periodSeconds` | How often to perform the probe | `10` |
| `envoy.startupProbe.timeoutSeconds` | When the probe times out | `5` |
| `envoy.startupProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded. | `3` |
| `envoy.startupProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed. | `1` |
| `envoy.customLivenessProbe` | Override default liveness probe | `{}` |
| `envoy.customReadinessProbe` | Override default readiness probe | `{}` |
| `envoy.customStartupProbe` | Override default startup probe | `{}` |
| `envoy.terminationGracePeriodSeconds` | Envoy termination grace period in seconds | `300` |
| `envoy.logLevel` | Envoy log level | `info` |
| `envoy.service.targetPorts` | Map the controller service HTTP/HTTPS port | `{}` |
| `envoy.service.type` | Type of Envoy service to create | `LoadBalancer` |
| `envoy.service.externalTrafficPolicy` | Envoy Service external cluster policy. If `envoy.service.type` is NodePort or LoadBalancer | `Local` |
| `envoy.service.labels` | Labels to add to te envoy service | `{}` |
| `envoy.service.clusterIP` | Internal envoy cluster service IP | `""` |
| `envoy.service.externalIPs` | Envoy service external IP addresses | `[]` |
| `envoy.service.loadBalancerIP` | IP address to assign to load balancer (if supported) | `""` |
| `envoy.service.loadBalancerSourceRanges` | List of IP CIDRs allowed access to load balancer (if supported) | `[]` |
| `envoy.service.ipFamilyPolicy` | , support SingleStack, PreferDualStack and RequireDualStack | `""` |
| `envoy.service.annotations` | Annotations for Envoy service | `{}` |
| `envoy.service.ports.http` | Sets service http port | `80` |
| `envoy.service.ports.https` | Sets service https port | `443` |
| `envoy.service.nodePorts.http` | HTTP Port. If `envoy.service.type` is NodePort and this is non-empty | `""` |
| `envoy.service.nodePorts.https` | HTTPS Port. If `envoy.service.type` is NodePort and this is non-empty | `""` |
| `envoy.service.extraPorts` | Extra ports to expose (normally used with the `sidecar` value) | `[]` |
| `envoy.service.sessionAffinity` | Session Affinity for Kubernetes service, can be "None" or "ClientIP" | `None` |
| `envoy.service.sessionAffinityConfig` | Additional settings for the sessionAffinity | `{}` |
| `envoy.useHostPort` | Enable/disable `hostPort` for TCP/80 and TCP/443 | `true` |
| `envoy.useHostIP` | Enable/disable `hostIP` | `false` |
| `envoy.hostPorts.http` | Sets `hostPort` http port | `80` |
| `envoy.hostPorts.https` | Sets `hostPort` https port | `443` |
| `envoy.hostIPs.http` | Sets `hostIP` http IP | `127.0.0.1` |
| `envoy.hostIPs.https` | Sets `hostIP` https IP | `127.0.0.1` |
| `envoy.containerPorts.http` | Sets http port inside Envoy pod (change this to >1024 to run envoy as a non-root user) | `8080` |
| `envoy.containerPorts.https` | Sets https port inside Envoy pod (change this to >1024 to run envoy as a non-root user) | `8443` |
| `envoy.initContainers` | Attach additional init containers to Envoy pods | `[]` |
| `envoy.sidecars` | Add additional sidecar containers to the Envoy pods | `[]` |
| `envoy.extraVolumes` | Array to add extra volumes | `[]` |
| `envoy.extraVolumeMounts` | Array to add extra mounts (normally used with extraVolumes) | `[]` |
| `envoy.extraEnvVars` | Array containing extra env vars to be added to all Envoy containers | `[]` |
| `envoy.extraEnvVarsCM` | ConfigMap containing extra env vars to be added to all Envoy containers | `""` |
| `envoy.extraEnvVarsSecret` | Secret containing extra env vars to be added to all Envoy containers | `""` |
### Default backend parameters
@@ -307,7 +307,7 @@ $ helm uninstall my-release
| `defaultBackend.enabled` | Enable a default backend based on NGINX | `false` |
| `defaultBackend.image.registry` | Default backend image registry | `docker.io` |
| `defaultBackend.image.repository` | Default backend image name | `bitnami/nginx` |
| `defaultBackend.image.tag` | Default backend image tag | `1.23.1-debian-11-r7` |
| `defaultBackend.image.tag` | Default backend image tag | `1.23.1-debian-11-r30` |
| `defaultBackend.image.digest` | Default backend image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag | `""` |
| `defaultBackend.image.pullPolicy` | Image pull policy | `IfNotPresent` |
| `defaultBackend.image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |
@@ -537,7 +537,7 @@ envoy:
This chart allows you to set your custom affinity using the `XXX.affinity` parameter(s). Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.nodeAffinityPreset` parameters.
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.nodeAffinityPreset` parameters.
## Troubleshooting
@@ -661,7 +661,7 @@ Most important changes are:
$ kubectl apply -f https://raw.githubusercontent.com/projectcontour/contour/release-{{version}}/examples/contour/01-crds.yaml
```
This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/master/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/main/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
## License
bitnami/discourse/Chart.yaml
+1 -1
View File
@@ -18,7 +18,7 @@ dependencies:
version: 2.x.x
description: Discourse is an open source discussion platform with built-in moderation and governance systems that let discussion communities protect themselves from bad actors even without official moderators.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/discourse
home: https://github.com/bitnami/charts/tree/main/bitnami/discourse
icon: https://bitnami.com/assets/stacks/discourse/img/discourse-stack-220x234.png
keywords:
- community
bitnami/discourse/README.md
+2 -2
View File
@@ -19,7 +19,7 @@ $ helm install my-release my-repo/discourse
This chart bootstraps a [Discourse](https://www.discourse.org/) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
It also packages [Bitnami Postgresql](https://github.com/bitnami/charts/tree/master/bitnami/postgresql) and [Bitnami Redis&reg;](https://github.com/bitnami/charts/tree/master/bitnami/redis) which are required as databases for the Discourse application.
It also packages [Bitnami Postgresql](https://github.com/bitnami/charts/tree/main/bitnami/postgresql) and [Bitnami Redis&reg;](https://github.com/bitnami/charts/tree/main/bitnami/redis) which are required as databases for the Discourse application.
Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
@@ -470,7 +470,7 @@ The chart also facilitates the creation of TLS secrets for use with the Ingress
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
## Persistence
bitnami/discourse/values.yaml
+2 -2
View File
@@ -792,7 +792,7 @@ networkPolicy:
## @section Discourse database parameters
## PostgreSQL chart configuration
## ref: https://github.com/bitnami/charts/blob/master/bitnami/postgresql/values.yaml
## ref: https://github.com/bitnami/charts/blob/main/bitnami/postgresql/values.yaml
## @param postgresql.enabled Switch to enable or disable the PostgreSQL helm chart
## @param postgresql.auth.enablePostgresUser Assign a password to the "postgres" admin user. Otherwise, remote access will be blocked for this user
## @param postgresql.auth.postgresPassword Password for the "postgres" admin user
@@ -842,7 +842,7 @@ externalDatabase:
## @section Redis&reg; parameters
## Redis&reg; chart configuration
## ref: https://github.com/bitnami/charts/blob/master/bitnami/redis/values.yaml
## ref: https://github.com/bitnami/charts/blob/main/bitnami/redis/values.yaml
## @param redis.enabled Switch to enable or disable the Redis&reg; helm
## @param redis.auth.enabled Enable password authentication
## @param redis.auth.password Redis&reg; password
bitnami/dokuwiki/Chart.yaml
+1 -1
View File
@@ -10,7 +10,7 @@ dependencies:
version: 2.x.x
description: DokuWiki is a standards-compliant wiki optimized for creating documentation. Designed to be simple to use for small organizations, it stores all data in plain text files so no database is required.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/dokuwiki
home: https://github.com/bitnami/charts/tree/main/bitnami/dokuwiki
icon: https://bitnami.com/assets/stacks/dokuwiki/img/dokuwiki-stack-220x234.png
keywords:
- dokuwiki
bitnami/dokuwiki/README.md
+3 -3
View File
@@ -7,7 +7,7 @@ DokuWiki is a standards-compliant wiki optimized for creating documentation. Des
[Overview of DokuWiki](https://www.splitbrain.org/projects/dokuwiki)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -276,7 +276,7 @@ Bitnami will release a new chart updating its containers if a new version of the
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
## Persistence
@@ -383,7 +383,7 @@ This version standardizes the way of defining Ingress rules. When configuring a
### To 7.0.0
This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/master/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/main/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
The [Bitnami Dokuwiki](https://github.com/bitnami/containers/tree/main/bitnami/dokuwiki) image was migrated to a "non-root" user approach. Previously the container ran as the `root` user and the Apache daemon was started as the `daemon` user. From now on, both the container and the Apache daemon run as user `1001`. You can revert this behavior by setting the parameters `containerSecurityContext.runAsUser` to `root`.
bitnami/drupal/Chart.yaml
+1 -1
View File
@@ -14,7 +14,7 @@ dependencies:
version: 2.x.x
description: Drupal is one of the most versatile open source content management systems in the world. It is pre-configured with the Ctools and Views modules, Drush and Let's Encrypt auto-configuration support.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/drupal
home: https://github.com/bitnami/charts/tree/main/bitnami/drupal
icon: https://bitnami.com/assets/stacks/drupal/img/drupal-stack-220x234.png
keywords:
- drupal
bitnami/drupal/README.md
+4 -4
View File
@@ -7,7 +7,7 @@ Drupal is one of the most versatile open source content management systems in th
[Overview of Drupal](http://drupal.org)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -19,7 +19,7 @@ $ helm install my-release my-repo/drupal
This chart bootstraps a [Drupal](https://github.com/bitnami/containers/tree/main/bitnami/drupal) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
It also packages the [Bitnami MariaDB chart](https://github.com/bitnami/charts/tree/master/bitnami/mariadb) which is required for bootstrapping a MariaDB deployment as a database for the Drupal application.
It also packages the [Bitnami MariaDB chart](https://github.com/bitnami/charts/tree/main/bitnami/mariadb) which is required for bootstrapping a MariaDB deployment as a database for the Drupal application.
Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
@@ -372,7 +372,7 @@ imagePullSecrets:
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
## Persistence
@@ -456,7 +456,7 @@ Additionally also updates the MariaDB subchart to it newest major, 10.0.0, which
### To 9.0.0
MariaDB dependency version was bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed unless an external database is used. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/master/bitnami/mariadb#to-800) for more information.
MariaDB dependency version was bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed unless an external database is used. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/main/bitnami/mariadb#to-800) for more information.
To upgrade to `9.0.0`, you have two alternatives:
bitnami/drupal/values.yaml
+2 -2
View File
@@ -549,7 +549,7 @@ ingress:
## @section Database parameters
## MariaDB chart configuration
## https://github.com/bitnami/charts/blob/master/bitnami/mariadb/values.yaml
## https://github.com/bitnami/charts/blob/main/bitnami/mariadb/values.yaml
##
mariadb:
## @param mariadb.enabled Whether to deploy a mariadb server to satisfy the applications database requirements
@@ -715,7 +715,7 @@ metrics:
type: ClusterIP
## @param metrics.service.ports.metrics Drupal exporter service port
##
ports:
ports:
metrics: 9117
## @param metrics.service.externalTrafficPolicy Drupal exporter service external traffic policy
## ref: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip
bitnami/ejbca/Chart.yaml
+1 -1
View File
@@ -16,7 +16,7 @@ dependencies:
version: 2.x.x
description: EJBCA is an enterprise class PKI Certificate Authority software, built using Java (JEE) technology.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/ejbca
home: https://github.com/bitnami/charts/tree/main/bitnami/ejbca
icon: https://bitnami.com/assets/stacks/ejbca/img/ejbca-stack-220x234.png
keywords:
- ejbca
bitnami/ejbca/README.md
+4 -4
View File
@@ -7,7 +7,7 @@ EJBCA is an enterprise class PKI Certificate Authority software, built using Jav
[Overview of EJBCA](http://www.ejbca.org)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -19,7 +19,7 @@ $ helm install my-release my-repo/ejbca
This chart bootstraps a [EJBCA](https://www.ejbca.org/) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
It also packages [Bitnami MariaDB](https://github.com/bitnami/charts/tree/master/bitnami/mariadb) as the required databases for the EJBCA application.
It also packages [Bitnami MariaDB](https://github.com/bitnami/charts/tree/main/bitnami/mariadb) as the required databases for the EJBCA application.
Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
@@ -298,7 +298,7 @@ Refer to the [chart documentation on using an external database](https://docs.bi
This chart allows you to set custom Pod affinity using the `affinity` parameter. Find more information about Pod affinity in the [Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
### Use a different EJBCA version
@@ -341,7 +341,7 @@ Additionally, updates the MariaDB subchart to it newest major, 10.0.0, which con
### To 1.0.0
MariaDB dependency version was bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed unless an external database is used. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/master/bitnami/mariadb#to-800) for more information.
MariaDB dependency version was bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed unless an external database is used. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/main/bitnami/mariadb#to-800) for more information.
To upgrade to `1.0.0`, you have two alternatives:
bitnami/ejbca/values.yaml
+1 -1
View File
@@ -548,7 +548,7 @@ ingress:
## @section Database parameters
## MariaDB chart configuration
## https://github.com/bitnami/charts/blob/master/bitnami/mariadb/values.yaml
## https://github.com/bitnami/charts/blob/main/bitnami/mariadb/values.yaml
##
mariadb:
## @param mariadb.enabled Whether to deploy a mariadb server to satisfy the applications database requirements.
bitnami/elasticsearch/Chart.yaml
+1 -1
View File
@@ -14,7 +14,7 @@ dependencies:
version: 2.x.x
description: Elasticsearch is a distributed search and analytics engine. It is used for web search, log monitoring, and real-time analytics. Ideal for Big Data applications.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/elasticsearch
home: https://github.com/bitnami/charts/tree/main/bitnami/elasticsearch
icon: https://bitnami.com/assets/stacks/elasticsearch/img/elasticsearch-stack-220x234.png
keywords:
- elasticsearch
bitnami/elasticsearch/README.md
+4 -4
View File
@@ -7,7 +7,7 @@ Elasticsearch is a distributed search and analytics engine. It is used for web s
[Overview of Elasticsearch](https://www.elastic.co/products/elasticsearch)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -799,7 +799,7 @@ initContainers:
This chart allows you to set your custom affinity using the `XXX.affinity` parameter(s). Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.nodeAffinityPreset` parameters.
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.nodeAffinityPreset` parameters.
## Persistence
@@ -860,7 +860,7 @@ The following values have been modified:
### To 17.0.0
This version bumps in a major the version of the Kibana Helm Chart bundled as dependecy, [here](https://github.com/bitnami/charts/tree/master/bitnami/kibana#to-900) you can see the changes implemented in this Kibana major version.
This version bumps in a major the version of the Kibana Helm Chart bundled as dependecy, [here](https://github.com/bitnami/charts/tree/main/bitnami/kibana#to-900) you can see the changes implemented in this Kibana major version.
### To 16.0.0
@@ -942,7 +942,7 @@ In [4dfac075aacf74405e31ae5b27df4369e84eb0b0](https://github.com/bitnami/charts/
### To 7.4.0
This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/master/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/main/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
### To 7.0.0
bitnami/elasticsearch/values.yaml
+1 -1
View File
@@ -2027,7 +2027,7 @@ metrics:
##
metricRelabelings: []
## @param metrics.serviceMonitor.selector ServiceMonitor selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
## selector:
## prometheus: my-prometheus
bitnami/etcd/Chart.yaml
+1 -1
View File
@@ -9,7 +9,7 @@ dependencies:
- bitnami-common
version: 2.x.x
description: etcd is a distributed key-value store designed to securely store data across a cluster. etcd is widely used in production on account of its reliability, fault-tolerance and ease of use.
home: https://github.com/bitnami/charts/tree/master/bitnami/etcd
home: https://github.com/bitnami/charts/tree/main/bitnami/etcd
icon: https://bitnami.com/assets/stacks/etcd/img/etcd-stack-220x234.png
keywords:
- etcd
bitnami/etcd/README.md
+3 -3
View File
@@ -439,7 +439,7 @@ There are cases where you may want to deploy extra objects, such a ConfigMap con
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
## Troubleshooting
@@ -449,7 +449,7 @@ Find more information about how to deal with common errors related to Bitnami's
### To 8.0.0
This version reverts the change in the previous major bump ([7.0.0](https://github.com/bitnami/charts/tree/master/bitnami/etcd#to-700)). Now the default `etcd` branch is `3.5` again once confirmed by the [etcd developers](https://github.com/etcd-io/etcd/tree/main/CHANGELOG#production-recommendation) that this version is production-ready once solved the data corruption issue.
This version reverts the change in the previous major bump ([7.0.0](https://github.com/bitnami/charts/tree/main/bitnami/etcd#to-700)). Now the default `etcd` branch is `3.5` again once confirmed by the [etcd developers](https://github.com/etcd-io/etcd/tree/main/CHANGELOG#production-recommendation) that this version is production-ready once solved the data corruption issue.
### To 7.0.0
@@ -485,7 +485,7 @@ Consequences:
### To 5.2.0
This version introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/master/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
This version introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/main/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
### To 5.0.0
bitnami/external-dns/Chart.yaml
+1 -1
View File
@@ -10,7 +10,7 @@ dependencies:
version: 2.x.x
description: ExternalDNS is a Kubernetes addon that configures public DNS servers with information about exposed Kubernetes services to make them discoverable.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/external-dns
home: https://github.com/bitnami/charts/tree/main/bitnami/external-dns
icon: https://bitnami.com/assets/stacks/external-dns/img/external-dns-stack-220x234.png
keywords:
- external-dns
bitnami/external-dns/README.md
+2 -2
View File
@@ -362,7 +362,7 @@ Bitnami will release a new chart updating its containers if a new version of the
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
### Using IRSA
If you are deploying to AWS EKS and you want to leverage [IRSA](https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html). You will need to override `fsGroup` and `runAsUser` with `65534`(nfsnobody) and `0` respectively. Otherwise service account token will not be properly mounted.
@@ -417,7 +417,7 @@ helm upgrade my-release -f my-values.yaml
### To 4.3.0
This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/master/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated thechart dependencies before executing any upgrade.
This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/main/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated thechart dependencies before executing any upgrade.
### To 4.0.0
bitnami/external-dns/values.yaml
+2 -2
View File
@@ -300,7 +300,7 @@ coredns:
## @param coredns.etcdTLS.secretName When using the CoreDNS provider, specify a name of existing Secret with etcd certs and keys
## ref: https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/security.md
## ref (secret creation):
## https://github.com/bitnami/charts/tree/master/bitnami/etcd#configure-certificates-for-client-communication
## https://github.com/bitnami/charts/tree/main/bitnami/etcd#configure-certificates-for-client-communication
##
secretName: "etcd-client-certs"
## @param coredns.etcdTLS.mountPath When using the CoreDNS provider, set destination dir to mount data from `coredns.etcdTLS.secretName` to
@@ -1005,7 +1005,7 @@ metrics:
##
scrapeTimeout: ""
## @param metrics.serviceMonitor.selector Additional labels for ServiceMonitor object
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
## e.g:
## selector:
## prometheus: my-prometheus
bitnami/fluentd/Chart.yaml
+1 -1
View File
@@ -10,7 +10,7 @@ dependencies:
version: 2.x.x
description: Fluentd collects events from various data sources and writes them to files, RDBMS, NoSQL, IaaS, SaaS, Hadoop and so on.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/fluentd
home: https://github.com/bitnami/charts/tree/main/bitnami/fluentd
icon: https://bitnami.com/assets/stacks/fluentd/img/fluentd-stack-220x234.png
keywords:
- fluentd
bitnami/fluentd/README.md
+2 -2
View File
@@ -493,7 +493,7 @@ Mounting additional `hostPath`s is sometimes required to deal with `/var/lib` be
This chart allows you to set your custom affinity using the `XXX.affinity` parameter(s). Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.nodeAffinityPreset` parameters.
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.nodeAffinityPreset` parameters.
## Troubleshooting
@@ -523,7 +523,7 @@ The new `tls.*` settings will now configure SSL/TLS certificates for the out_for
### To 3.1.0
This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/master/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/main/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
### To 3.0.0
bitnami/fluentd/values.yaml
+1 -1
View File
@@ -1335,7 +1335,7 @@ metrics:
##
metricRelabelings: []
## @param metrics.serviceMonitor.selector Prometheus instance selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
## e.g:
## selector:
## prometheus: my-prometheus
bitnami/geode/Chart.yaml
+1 -1
View File
@@ -9,7 +9,7 @@ dependencies:
- bitnami-common
version: 2.x.x
description: Apache Geode is a data management platform that provides advanced capabilities for data-intensive applications.
home: https://github.com/bitnami/charts/tree/master/bitnami/geode
home: https://github.com/bitnami/charts/tree/main/bitnami/geode
icon: https://bitnami.com/assets/stacks/geode/img/geode-stack-220x234.png
keywords:
- apache
bitnami/geode/README.md
+3 -3
View File
@@ -7,7 +7,7 @@ Apache Geode is a data management platform that provides advanced capabilities f
[Overview of Apache Geode](https://geode.apache.org/)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -450,7 +450,7 @@ Bitnami will release a new chart updating its containers if a new version of the
### Ingress
This chart provides support for Ingress resources. If you have an ingress controller installed on your cluster, such as [nginx-ingress-controller](https://github.com/bitnami/charts/tree/master/bitnami/nginx-ingress-controller) or [contour](https://github.com/bitnami/charts/tree/master/bitnami/contour) you can utilize the ingress controller to serve your application.
This chart provides support for Ingress resources. If you have an ingress controller installed on your cluster, such as [nginx-ingress-controller](https://github.com/bitnami/charts/tree/main/bitnami/nginx-ingress-controller) or [contour](https://github.com/bitnami/charts/tree/main/bitnami/contour) you can utilize the ingress controller to serve your application.
To enable Ingress integration, set `ingress.enabled` to `true`. The `ingress.hostname` property can be used to set the host name. The `ingress.tls` parameter can be used to add the TLS configuration for this host. It is also possible to have more than one host, with a separate TLS configuration for each host. [Learn more about configuring and using Ingress](https://docs.bitnami.com/kubernetes/infrastructure/geode/configuration/configure-ingress/).
@@ -483,7 +483,7 @@ If additional containers are needed in the same pod as geode (such as additional
This chart allows you to set your custom affinity using the `XXX.affinity` parameter(s). Find more information about Pod affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.nodeAffinityPreset` parameters.
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.nodeAffinityPreset` parameters.
> Note: XXX is placeholder you need to replace with the actual component(s).
bitnami/geode/values.yaml
+1 -1
View File
@@ -1124,7 +1124,7 @@ metrics:
##
relabelings: []
## @param metrics.serviceMonitor.selector Prometheus instance selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
selector: {}
## @param metrics.serviceMonitor.honorLabels honorLabels chooses the metric's labels on collisions with target labels
bitnami/ghost/Chart.yaml
+1 -1
View File
@@ -16,7 +16,7 @@ dependencies:
version: 2.x.x
description: Ghost is an open source publishing platform designed to create blogs, magazines, and news sites. It includes a simple markdown editor with preview, theming, and SEO built-in to simplify editing.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/ghost
home: https://github.com/bitnami/charts/tree/main/bitnami/ghost
icon: https://bitnami.com/assets/stacks/ghost/img/ghost-stack-220x234.png
keywords:
- ghost
bitnami/ghost/README.md
+7 -7
View File
@@ -7,7 +7,7 @@ Ghost is an open source publishing platform designed to create blogs, magazines,
[Overview of Ghost](https://ghost.org/)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -19,7 +19,7 @@ $ helm install my-release my-repo/ghost
This chart bootstraps a [Ghost](https://github.com/bitnami/containers/tree/main/bitnami/ghost) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
It also packages the [Bitnami MySQL chart](https://github.com/bitnami/charts/tree/master/bitnami/mysql) which is required for bootstrapping a MySQL deployment for the database requirements of the Ghost application.
It also packages the [Bitnami MySQL chart](https://github.com/bitnami/charts/tree/main/bitnami/mysql) which is required for bootstrapping a MySQL deployment for the database requirements of the Ghost application.
Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
@@ -337,7 +337,7 @@ Refer to the [documentation on using an external database with Ghost](https://do
### Configure Ingress
This chart provides support for Ingress resources. If you have an ingress controller installed on your cluster, such as [nginx-ingress-controller](https://github.com/bitnami/charts/tree/master/bitnami/nginx-ingress-controller) or [contour](https://github.com/bitnami/charts/tree/master/bitnami/contour) you can utilize the ingress controller to serve your application.
This chart provides support for Ingress resources. If you have an ingress controller installed on your cluster, such as [nginx-ingress-controller](https://github.com/bitnami/charts/tree/main/bitnami/nginx-ingress-controller) or [contour](https://github.com/bitnami/charts/tree/main/bitnami/contour) you can utilize the ingress controller to serve your application.
To enable Ingress integration, set `ingress.enabled` to `true`. The `ingress.hostname` property can be used to set the host name. The `ingress.tls` parameter can be used to add the TLS configuration for this host. It is also possible to have more than one host, with a separate TLS configuration for each host. [Learn more about configuring and using Ingress](https://docs.bitnami.com/kubernetes/apps/ghost/configuration/configure-ingress/).
@@ -371,7 +371,7 @@ There are cases where you may want to deploy extra objects, such a ConfigMap con
This chart allows you to set custom Pod affinity using the `affinity` parameter(s). Find more information about Pod affinity in the [Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, you can use the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
## Persistence
@@ -397,7 +397,7 @@ This major release bumps the MariaDB version to 10.6. Follow the [upstream instr
### To 16.0.0
This major release updates the MariaDB subchart to its newest major, 10.0.0. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/master/bitnami/mariadb#to-1000) for more information.
This major release updates the MariaDB subchart to its newest major, 10.0.0. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/main/bitnami/mariadb#to-1000) for more information.
### To 15.0.0
@@ -452,7 +452,7 @@ Please read the update notes carefully.
**2. Updated MariaDB dependency version**
In this major the MariaDB dependency version was also bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed unless an external database is used. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/master/bitnami/mariadb#to-800) for more information.
In this major the MariaDB dependency version was also bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed unless an external database is used. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/main/bitnami/mariadb#to-800) for more information.
To upgrade to `11.0.0`, it should be done reusing the PVCs used to hold both the MariaDB and Ghost data on your previous release. To do so, follow the instructions below (the following example assumes that the release name is `ghost`):
@@ -500,7 +500,7 @@ mariadb 12:13:25.01 INFO ==> Running mysql_upgrade
### To 10.0.0
This version introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/master/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
This version introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/main/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
Also, `allowEmptyPassword` has changed its value type from string to boolean, if you were using it please make sure that you are passing the proper value.
bitnami/ghost/values.yaml
+1 -1
View File
@@ -599,7 +599,7 @@ volumePermissions:
## @section Database Parameters
## MySQL chart configuration
## ref: https://github.com/bitnami/charts/blob/master/bitnami/mysql/values.yaml
## ref: https://github.com/bitnami/charts/blob/main/bitnami/mysql/values.yaml
##
mysql:
## @param mysql.enabled Deploy a MySQL server to satisfy the applications database requirements
bitnami/grafana-loki/README.md
+3 -3
View File
@@ -2,12 +2,12 @@
# Grafana Loki packaged by Bitnami
Grafana Loki is a horizontally scalable, highly available, and multi-tenant log aggregation system. It provides real-time long tailing and full persistence to object storage.
Grafana Loki is a horizontally scalable, highly available, and multi-tenant log aggregation system. It provides real-time long tailing and full persistence to object storage.
[Overview of Grafana Loki](https://grafana.com/oss/loki/)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -1281,7 +1281,7 @@ If additional containers are needed in the same pod as grafana-loki (such as add
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters inside each of the subsections: `distributor`, `compactor`, `ingester`, `querier`, `queryFrontend` and `vulture`.
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters inside each of the subsections: `distributor`, `compactor`, `ingester`, `querier`, `queryFrontend` and `vulture`.
### External cache support
bitnami/grafana-loki/values.yaml
+1 -1
View File
@@ -3744,7 +3744,7 @@ metrics:
##
labels: {}
## @param metrics.serviceMonitor.selector Prometheus instance selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
selector: {}
## @param metrics.serviceMonitor.relabelings RelabelConfigs to apply to samples before scraping
bitnami/grafana-operator/values.yaml
+1 -1
View File
@@ -348,7 +348,7 @@ operator:
##
relabelings: []
## @param operator.prometheus.serviceMonitor.selector ServiceMonitor selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
## selector:
## prometheus: my-prometheus
bitnami/grafana-tempo/README.md
+1 -1
View File
@@ -880,7 +880,7 @@ If additional containers are needed in the same pod as grafana-tempo (such as ad
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters inside each of the subsections: `distributor`, `compactor`, `ingester`, `querier`, `queryFrontend` and `vulture`.
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters inside each of the subsections: `distributor`, `compactor`, `ingester`, `querier`, `queryFrontend` and `vulture`.
### External cache support
bitnami/grafana-tempo/values.yaml
+1 -1
View File
@@ -2412,7 +2412,7 @@ metrics:
##
labels: {}
## @param metrics.serviceMonitor.selector Prometheus instance selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
selector: {}
## @param metrics.serviceMonitor.relabelings RelabelConfigs to apply to samples before scraping
bitnami/grafana/Chart.yaml
+1 -1
View File
@@ -10,7 +10,7 @@ dependencies:
version: 2.x.x
description: Grafana is an open source metric analytics and visualization suite for visualizing time series data that supports various types of data sources.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/grafana
home: https://github.com/bitnami/charts/tree/main/bitnami/grafana
icon: https://bitnami.com/assets/stacks/grafana/img/grafana-stack-220x234.png
keywords:
- analytics
bitnami/grafana/README.md
+2 -2
View File
@@ -610,7 +610,7 @@ More information about Grafana HA [here](https://grafana.com/docs/tutorials/ha_s
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
## Persistence
@@ -642,7 +642,7 @@ helm upgrade <release-name> my-repo/grafana
### To 4.1.0
This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/master/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/main/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
### To 4.0.0
bitnami/grafana/values.yaml
+2 -2
View File
@@ -761,7 +761,7 @@ metrics:
##
scrapeTimeout: ""
## @param metrics.serviceMonitor.selector Prometheus instance selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
## e.g:
## selector:
## prometheus: my-prometheus
@@ -1066,7 +1066,7 @@ imageRenderer:
##
metricRelabelings: []
## @param imageRenderer.metrics.serviceMonitor.selector ServiceMonitor selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
## selector:
## prometheus: my-prometheus
bitnami/haproxy-intel/README.md
+2 -2
View File
@@ -75,7 +75,7 @@ The command removes all the Kubernetes components associated with the chart and
| `haproxy.image.pullSecrets` | HAProxy image pull secrets | `[]` |
HAProxy is installed as a subchart, meaning that the whole list of parameters is defined in [bitnami/haproxy](https://github.com/bitnami/charts/tree/master/bitnami/haproxy). Please, note that parameters from the subchart should be prefixed with `haproxy.` in this chart.
HAProxy is installed as a subchart, meaning that the whole list of parameters is defined in [bitnami/haproxy](https://github.com/bitnami/charts/tree/main/bitnami/haproxy). Please, note that parameters from the subchart should be prefixed with `haproxy.` in this chart.
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
@@ -139,7 +139,7 @@ Refer to the chart documentation for more information on, and examples of, confi
This chart allows you to set custom Pod affinity using the `haproxy.affinity` parameter. Find more information about Pod affinity in the [Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `haproxy.podAffinityPreset`, `haproxy.podAntiAffinityPreset`, or `haproxy.nodeAffinityPreset` parameters.
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `haproxy.podAffinityPreset`, `haproxy.podAntiAffinityPreset`, or `haproxy.nodeAffinityPreset` parameters.
## Troubleshooting
bitnami/haproxy-intel/values.yaml
+1 -1
View File
@@ -19,7 +19,7 @@ global:
## @section HAProxy chart parameters
## Parameters for the bitnami/haproxy chart deployed by this chart
## For a full list, see: https://github.com/bitnami/charts/tree/master/bitnami/haproxy
## For a full list, see: https://github.com/bitnami/charts/tree/main/bitnami/haproxy
## Note that parameters from the bitnami/haproxy chart should be prefixed with 'haproxy.'
##
bitnami/haproxy/README.md
+1 -1
View File
@@ -245,7 +245,7 @@ Refer to the chart documentation for more information on, and examples of, confi
This chart allows you to set custom Pod affinity using the `affinity` parameter. Find more information about Pod affinity in the [Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
## Troubleshooting
bitnami/harbor/Chart.yaml
+1 -1
View File
@@ -18,7 +18,7 @@ dependencies:
version: 2.x.x
description: Harbor is an open source trusted cloud-native registry to store, sign, and scan content. It adds functionalities like security, identity, and management to the open source Docker distribution.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/harbor
home: https://github.com/bitnami/charts/tree/main/bitnami/harbor
icon: https://bitnami.com/assets/stacks/harbor-core/img/harbor-core-stack-220x234.png
keywords:
- docker
bitnami/harbor/README.md
+3 -3
View File
@@ -7,7 +7,7 @@ Harbor is an open source trusted cloud-native registry to store, sign, and scan
[Overview of Harbor](https://goharbor.io/)
## TL;DR
```bash
@@ -17,7 +17,7 @@ helm install my-release my-repo/harbor
## Introduction
This [Helm](https://github.com/kubernetes/helm) chart installs [Harbor](https://github.com/goharbor/harbor) in a Kubernetes cluster. Welcome to [contribute](https://github.com/bitnami/charts/blob/master/CONTRIBUTING.md) to Helm Chart for Harbor.
This [Helm](https://github.com/kubernetes/helm) chart installs [Harbor](https://github.com/goharbor/harbor) in a Kubernetes cluster. Welcome to [contribute](https://github.com/bitnami/charts/blob/main/CONTRIBUTING.md) to Helm Chart for Harbor.
This Helm chart has been developed based on [goharbor/harbor-helm](https://github.com/goharbor/harbor-helm) chart but including some features common to the Bitnami chart library.
For example, the following changes have been introduced:
@@ -1287,7 +1287,7 @@ Secrets and certificates must be setup to avoid changes on every Helm upgrade (s
This chart allows you to set your custom affinity using the `XXX.affinity` parameter(s). Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.nodeAffinityPreset` parameters.
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.nodeAffinityPreset` parameters.
### Adjust permissions of persistent volume mountpoint
bitnami/harbor/values.yaml
+3 -3
View File
@@ -3666,7 +3666,7 @@ exporter:
##
## PostgreSQL chart configuration
## ref: https://github.com/bitnami/charts/blob/master/bitnami/postgresql/values.yaml
## ref: https://github.com/bitnami/charts/blob/main/bitnami/postgresql/values.yaml
## @param postgresql.enabled Switch to enable or disable the PostgreSQL helm chart
## @param postgresql.auth.enablePostgresUser Assign a password to the "postgres" admin user. Otherwise, remote access will be blocked for this user
## @param postgresql.auth.postgresPassword Password for the "postgres" admin user
@@ -3746,7 +3746,7 @@ externalDatabase:
##
## Redis&reg; chart configuration
## ref: https://github.com/bitnami/charts/blob/master/bitnami/redis/values.yaml
## ref: https://github.com/bitnami/charts/blob/main/bitnami/redis/values.yaml
## @param redis.enabled Switch to enable or disable the Redis&reg; helm
## @param redis.auth.enabled Enable password authentication
## @param redis.auth.password Redis&reg; password
@@ -3826,7 +3826,7 @@ metrics:
##
labels: {}
## @param metrics.serviceMonitor.selector Prometheus instance selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
selector: {}
## @param metrics.serviceMonitor.relabelings RelabelConfigs to apply to samples before scraping
bitnami/influxdb/Chart.yaml
+1 -1
View File
@@ -10,7 +10,7 @@ dependencies:
version: 2.x.x
description: InfluxDB(TM) is an open source time-series database. It is a core component of the TICK (Telegraf, InfluxDB(TM), Chronograf, Kapacitor) stack.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/influxdb
home: https://github.com/bitnami/charts/tree/main/bitnami/influxdb
icon: https://bitnami.com/assets/stacks/influxdb/img/influxdb-stack-220x234.png
keywords:
- influxdb
bitnami/influxdb/README.md
+2 -2
View File
@@ -421,7 +421,7 @@ The allowed extensions are `.sh`, and `.txt`.
This chart allows you to set your custom affinity using the `XXX.affinity` parameter(s). Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.nodeAffinityPreset` parameters.
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.nodeAffinityPreset` parameters.
## Persistence
@@ -543,7 +543,7 @@ $ helm upgrade influxdb my-repo/influxdb --set image.tag=1.8.3-debian-10-r99 \
### To 1.1.0
This version introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/master/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
This version introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/main/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
### To 1.0.0
bitnami/influxdb/values.yaml
+1 -1
View File
@@ -717,7 +717,7 @@ metrics:
##
metricRelabelings: []
## @param metrics.serviceMonitor.selector Prometheus instance selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
## e.g:
## selector:
## prometheus: my-prometheus
bitnami/jasperreports/Chart.yaml
+1 -1
View File
@@ -14,7 +14,7 @@ dependencies:
version: 2.x.x
description: JasperReports Server is a stand-alone and embeddable reporting server. It is a central information hub, with reporting and analytics that can be embedded into web and mobile applications.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/jasperreports
home: https://github.com/bitnami/charts/tree/main/bitnami/jasperreports
icon: https://bitnami.com/assets/stacks/jasperserver/img/jasperserver-stack-220x234.png
keywords:
- business intelligence
bitnami/jasperreports/README.md
+5 -5
View File
@@ -7,7 +7,7 @@ JasperReports Server is a stand-alone and embeddable reporting server. It is a c
[Overview of JasperReports](http://community.jaspersoft.com/project/jasperreports-server)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -19,7 +19,7 @@ $ helm install my-release my-repo/jasperreports
This chart bootstraps a [JasperReports](https://github.com/bitnami/containers/tree/main/bitnami/jasperreports) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
It also packages the [Bitnami MariaDB chart](https://github.com/bitnami/charts/tree/master/bitnami/mariadb) which bootstraps a MariaDB deployment required by the JasperReports application.
It also packages the [Bitnami MariaDB chart](https://github.com/bitnami/charts/tree/main/bitnami/mariadb) which bootstraps a MariaDB deployment required by the JasperReports application.
Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
@@ -319,7 +319,7 @@ initContainers:
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
## Troubleshooting
@@ -341,7 +341,7 @@ Affected values:
- `service.nodePort` was deprecated, we recommend using `service.nodePorts.http` instead .
- `containerPort` was deprecated, we recommend using `containerPorts.http` instead.
Additionally updates the MariaDB subchart to it newest major, 10.0.0, which contains similar changes. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/master/bitnami/mariadb#to-1000) for more information.
Additionally updates the MariaDB subchart to it newest major, 10.0.0, which contains similar changes. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/main/bitnami/mariadb#to-1000) for more information.
### To 11.0.0
@@ -409,7 +409,7 @@ Please read the update notes carefully.
**2. Updated MariaDB dependency version**
In this major the MariaDB dependency version was also bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed unless an external database is used. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/master/bitnami/mariadb#to-800) for more information.
In this major the MariaDB dependency version was also bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed unless an external database is used. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/main/bitnami/mariadb#to-800) for more information.
To upgrade to `9.0.0`, it should be done reusing the PVCs used to hold both the MariaDB and JasperReports data on your previous release. To do so, follow the instructions below (the following example assumes that the release name is `jasperreports` and that a `rootUser.password` was defined for MariaDB in `values.yaml` when the chart was first installed):
bitnami/jasperreports/values.yaml
+1 -1
View File
@@ -522,7 +522,7 @@ ingress:
##
## MariaDB chart configuration
## https://github.com/bitnami/charts/blob/master/bitnami/mariadb/values.yaml
## https://github.com/bitnami/charts/blob/main/bitnami/mariadb/values.yaml
##
mariadb:
## @param mariadb.enabled Whether to use the MariaDB chart
bitnami/jenkins/Chart.yaml
+1 -1
View File
@@ -10,7 +10,7 @@ dependencies:
version: 2.x.x
description: Jenkins is an open source Continuous Integration and Continuous Delivery (CI/CD) server designed to automate the building, testing, and deploying of any software project.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/jenkins
home: https://github.com/bitnami/charts/tree/main/bitnami/jenkins
icon: https://bitnami.com/assets/stacks/jenkins/img/jenkins-stack-220x234.png
keywords:
- jenkins
bitnami/jenkins/README.md
+4 -4
View File
@@ -7,7 +7,7 @@ Jenkins is an open source Continuous Integration and Continuous Delivery (CI/CD)
[Overview of Jenkins](http://jenkins-ci.org/)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -254,7 +254,7 @@ Bitnami will release a new chart updating its containers if a new version of the
### Configure Ingress
This chart provides support for Ingress resources. If you have an ingress controller installed on your cluster, such as [nginx-ingress-controller](https://github.com/bitnami/charts/tree/master/bitnami/nginx-ingress-controller) or [contour](https://github.com/bitnami/charts/tree/master/bitnami/contour) you can utilize the ingress controller to serve your application.
This chart provides support for Ingress resources. If you have an ingress controller installed on your cluster, such as [nginx-ingress-controller](https://github.com/bitnami/charts/tree/main/bitnami/nginx-ingress-controller) or [contour](https://github.com/bitnami/charts/tree/main/bitnami/contour) you can utilize the ingress controller to serve your application.
To enable Ingress integration, set `ingress.enabled` to `true`. The `ingress.hostname` property can be used to set the host name. The `ingress.tls` parameter can be used to add the TLS configuration for this host. It is also possible to have more than one host, with a separate TLS configuration for each host. [Learn more about configuring and using Ingress](https://docs.bitnami.com/kubernetes/apps/jenkins/configuration/configure-ingress/).
@@ -288,7 +288,7 @@ There are cases where you may want to deploy extra objects, such a ConfigMap con
This chart allows you to set custom Pod affinity using the `XXX.affinity` parameter(s). Find more information about Pod affinity in the [Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.nodeAffinityPreset` parameters.
As an alternative, you can use the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.nodeAffinityPreset` parameters.
## Persistence
@@ -356,7 +356,7 @@ $ helm upgrade jenkins my-repo/jenkins --set jenkinsPassword=$JENKINS_PASSWORD
### To 6.1.0
This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/master/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/main/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
### To 6.0.0
bitnami/joomla/Chart.yaml
+1 -1
View File
@@ -14,7 +14,7 @@ dependencies:
version: 2.x.x
description: Joomla! is an award winning open source CMS platform for building websites and applications. It includes page caching, page compression and Let's Encrypt auto-configuration support.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/joomla
home: https://github.com/bitnami/charts/tree/main/bitnami/joomla
icon: https://bitnami.com/assets/stacks/joomla/img/joomla-stack-220x234.png
keywords:
- joomla
bitnami/joomla/README.md
+3 -3
View File
@@ -19,7 +19,7 @@ $ helm install my-release my-repo/joomla
This chart bootstraps a [Joomla!](https://github.com/bitnami/containers/tree/main/bitnami/joomla) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
It also packages the [Bitnami MariaDB chart](https://github.com/bitnami/charts/tree/master/bitnami/mariadb) which is required for bootstrapping a MariaDB deployment for the database requirements of the Joomla! application.
It also packages the [Bitnami MariaDB chart](https://github.com/bitnami/charts/tree/main/bitnami/mariadb) which is required for bootstrapping a MariaDB deployment for the database requirements of the Joomla! application.
Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
@@ -336,7 +336,7 @@ ingress:
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
## Persistence
@@ -410,7 +410,7 @@ Please read the update notes carefully.
**2. Updated MariaDB dependency version**
In this major the MariaDB dependency version was also bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed unless an external database is used. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/master/bitnami/mariadb#to-800) for more information.
In this major the MariaDB dependency version was also bumped to a new major version that introduces several incompatilibites. Therefore, backwards compatibility is not guaranteed unless an external database is used. Check [MariaDB Upgrading Notes](https://github.com/bitnami/charts/tree/main/bitnami/mariadb#to-800) for more information.
To upgrade to `9.0.0`, it should be done reusing the PVCs used to hold both the MariaDB and Joomla data on your previous release. To do so, follow the instructions below (the following example assumes that the release name is `joomla`):
bitnami/joomla/values.yaml
+1 -1
View File
@@ -522,7 +522,7 @@ ingress:
##
## MariaDB chart configuration
## https://github.com/bitnami/charts/blob/master/bitnami/mariadb/values.yaml
## https://github.com/bitnami/charts/blob/main/bitnami/mariadb/values.yaml
##
mariadb:
## @param mariadb.enabled Whether to deploy a mariadb server to satisfy the applications database requirements. To use an external database set this to false and configure the externalDatabase parameters
bitnami/jupyterhub/values.yaml
+3 -3
View File
@@ -606,7 +606,7 @@ hub:
##
labels: {}
## @param hub.metrics.serviceMonitor.selector Prometheus instance selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
selector: {}
## @param hub.metrics.serviceMonitor.relabelings RelabelConfigs to apply to samples before scraping
@@ -1189,7 +1189,7 @@ proxy:
##
labels: {}
## @param proxy.metrics.serviceMonitor.selector Prometheus instance selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
selector: {}
## @param proxy.metrics.serviceMonitor.relabelings RelabelConfigs to apply to samples before scraping
@@ -1591,7 +1591,7 @@ auxiliaryImage:
## @section JupyterHub database parameters
## PostgreSQL chart configuration
## ref: https://github.com/bitnami/charts/blob/master/bitnami/postgresql/values.yaml
## ref: https://github.com/bitnami/charts/blob/main/bitnami/postgresql/values.yaml
## @param postgresql.enabled Switch to enable or disable the PostgreSQL helm chart
## @param postgresql.auth.username Name for a custom user to create
## @param postgresql.auth.password Password for the custom user to create
bitnami/kafka/Chart.yaml
+1 -1
View File
@@ -14,7 +14,7 @@ dependencies:
version: 2.x.x
description: Apache Kafka is a distributed streaming platform designed to build real-time pipelines and can be used as a message broker or as a replacement for a log aggregation solution for big data applications.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/kafka
home: https://github.com/bitnami/charts/tree/main/bitnami/kafka
icon: https://bitnami.com/assets/stacks/kafka/img/kafka-stack-220x234.png
keywords:
- kafka
bitnami/kafka/README.md
+6 -6
View File
@@ -7,7 +7,7 @@ Apache Kafka is a distributed streaming platform designed to build real-time pip
[Overview of Apache Kafka](http://kafka.apache.org/)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -735,7 +735,7 @@ sidecars:
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
### Deploying extra resources
@@ -844,11 +844,11 @@ This major updates Kafka to its newest version, 3.3.x. For more information, ple
### To 18.0.0
This major updates the Zookeeper subchart to it newest major, 10.0.0. For more information on this subchart's major, please refer to [zookeeper upgrade notes](https://github.com/bitnami/charts/tree/master/bitnami/zookeeper#to-1000).
This major updates the Zookeeper subchart to it newest major, 10.0.0. For more information on this subchart's major, please refer to [zookeeper upgrade notes](https://github.com/bitnami/charts/tree/main/bitnami/zookeeper#to-1000).
### To 16.0.0
This major updates the Zookeeper subchart to it newest major, 9.0.0. For more information on this subchart's major, please refer to [zookeeper upgrade notes](https://github.com/bitnami/charts/tree/master/bitnami/zookeeper#to-900).
This major updates the Zookeeper subchart to it newest major, 9.0.0. For more information on this subchart's major, please refer to [zookeeper upgrade notes](https://github.com/bitnami/charts/tree/main/bitnami/zookeeper#to-900).
### To 15.0.0
@@ -893,11 +893,11 @@ See [PR#7114](https://github.com/bitnami/charts/pull/7114) for more info about t
### To 13.0.0
This major updates the Zookeeper subchart to it newest major, 7.0.0, which renames all TLS-related settings. For more information on this subchart's major, please refer to [zookeeper upgrade notes](https://github.com/bitnami/charts/tree/master/bitnami/zookeeper#to-700).
This major updates the Zookeeper subchart to it newest major, 7.0.0, which renames all TLS-related settings. For more information on this subchart's major, please refer to [zookeeper upgrade notes](https://github.com/bitnami/charts/tree/main/bitnami/zookeeper#to-700).
### To 12.2.0
This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/master/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/main/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
### To 12.0.0
bitnami/kafka/values.yaml
+2 -2
View File
@@ -1429,7 +1429,7 @@ metrics:
##
labels: {}
## @param metrics.serviceMonitor.selector Prometheus instance selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
selector: {}
## @param metrics.serviceMonitor.relabelings RelabelConfigs to apply to samples before scraping
@@ -1672,7 +1672,7 @@ provisioning:
## @section ZooKeeper chart parameters
## ZooKeeper chart configuration
## https://github.com/bitnami/charts/blob/master/bitnami/zookeeper/values.yaml
## https://github.com/bitnami/charts/blob/main/bitnami/zookeeper/values.yaml
##
zookeeper:
## @param zookeeper.enabled Switch to enable or disable the ZooKeeper helm chart
bitnami/keycloak/README.md
+3 -3
View File
@@ -7,7 +7,7 @@ Keycloak is a high performance Java-based identity and access management solutio
[Overview of Keycloak](https://www.keycloak.org/)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -407,11 +407,11 @@ There are cases where you may want to deploy extra objects, such a ConfigMap con
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
### Configure Ingress
This chart provides support for Ingress resources. If you have an ingress controller installed on your cluster, such as [nginx-ingress-controller](https://github.com/bitnami/charts/tree/master/bitnami/nginx-ingress-controller) or [contour](https://github.com/bitnami/charts/tree/master/bitnami/contour) you can utilize the ingress controller to serve your application.
This chart provides support for Ingress resources. If you have an ingress controller installed on your cluster, such as [nginx-ingress-controller](https://github.com/bitnami/charts/tree/main/bitnami/nginx-ingress-controller) or [contour](https://github.com/bitnami/charts/tree/main/bitnami/contour) you can utilize the ingress controller to serve your application.
To enable Ingress integration, set `ingress.enabled` to `true`. The `ingress.hostname` property can be used to set the host name. The `ingress.tls` parameter can be used to add the TLS configuration for this host. It is also possible to have more than one host, with a separate TLS configuration for each host. [Learn more about configuring and using Ingress](https://docs.bitnami.com/kubernetes/apps/keycloak/configuration/configure-ingress/).
bitnami/keycloak/values.yaml
+2 -2
View File
@@ -768,7 +768,7 @@ metrics:
##
labels: {}
## @param metrics.serviceMonitor.selector Prometheus instance selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
selector: {}
## @param metrics.serviceMonitor.relabelings RelabelConfigs to apply to samples before scraping
@@ -965,7 +965,7 @@ keycloakConfigCli:
## @section Database parameters
## PostgreSQL chart configuration
## ref: https://github.com/bitnami/charts/blob/master/bitnami/postgresql/values.yaml
## ref: https://github.com/bitnami/charts/blob/main/bitnami/postgresql/values.yaml
## @param postgresql.enabled Switch to enable or disable the PostgreSQL helm chart
## @param postgresql.auth.username Name for a custom user to create
## @param postgresql.auth.password Password for the custom user to create
bitnami/kiam/README.md
+2 -2
View File
@@ -7,7 +7,7 @@ kiam is a proxy that captures AWS Metadata API requests. It allows AWS IAM roles
[Overview of Kiam](https://github.com/uswitch/kiam)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -405,7 +405,7 @@ There are cases where you may want to deploy extra objects, such a ConfigMap con
This chart allows you to set your custom affinity using the `server.affinity` and `agent.affinity` parameters. Find more information about Pod affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `server.podAffinityPreset`, `agent.podAffinityPreset`, `server.podAntiAffinityPreset`, `agent.podAntiAffinityPreset`, or `server.nodeAffinityPreset` and `agent.nodeAffinityPreset` parameters.
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `server.podAffinityPreset`, `agent.podAffinityPreset`, `server.podAntiAffinityPreset`, `agent.podAntiAffinityPreset`, or `server.nodeAffinityPreset` and `agent.nodeAffinityPreset` parameters.
### Configure TLS Secrets
bitnami/kiam/values.yaml
+2 -2
View File
@@ -482,7 +482,7 @@ server:
##
scrapeTimeout: ""
## @param server.metrics.serviceMonitor.selector metrics service selector
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
selector: {}
## @param server.metrics.serviceMonitor.labels Extra labels for the ServiceMonitor
@@ -902,7 +902,7 @@ agent:
##
scrapeTimeout: ""
## @param agent.metrics.serviceMonitor.selector metrics service selector
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
selector: {}
## @param agent.metrics.serviceMonitor.labels Extra labels for the ServiceMonitor
bitnami/kibana/Chart.yaml
+1 -1
View File
@@ -10,7 +10,7 @@ dependencies:
version: 2.x.x
description: Kibana is an open source, browser based analytics and search dashboard for Elasticsearch. Kibana strives to be easy to get started with, while also being flexible and powerful.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/kibana
home: https://github.com/bitnami/charts/tree/main/bitnami/kibana
icon: https://bitnami.com/assets/stacks/kibana/img/kibana-stack-220x234.png
keywords:
- kibana
bitnami/kibana/README.md
+4 -4
View File
@@ -7,7 +7,7 @@ Kibana is an open source, browser based analytics and search dashboard for Elast
[Overview of Kibana](https://www.elastic.co/products/kibana)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -347,7 +347,7 @@ Refer to the chart documentation for more information on, and examples of, confi
#### Add a sample Elasticsearch container as sidecar
This chart requires an Elasticsearch instance to work. For production, the options are to use an already existing Elasticsearch instance or deploy the [Elasticsearch chart](https://github.com/bitnami/charts/tree/master/bitnami/elasticsearch) with the [`global.kibanaEnabled=true` parameter](https://github.com/bitnami/charts/tree/master/bitnami/elasticsearch#enable-bundled-kibana).
This chart requires an Elasticsearch instance to work. For production, the options are to use an already existing Elasticsearch instance or deploy the [Elasticsearch chart](https://github.com/bitnami/charts/tree/main/bitnami/elasticsearch) with the [`global.kibanaEnabled=true` parameter](https://github.com/bitnami/charts/tree/main/bitnami/elasticsearch#enable-bundled-kibana).
For testing purposes, use a sidecar Elasticsearch container setting the following parameters during the Kibana chart installation:
@@ -365,7 +365,7 @@ sidecars[0].ports[0].containerPort=9200
This chart allows you to set custom Pod affinity using the `affinity` parameter. Find more information about Pod affinity in the [Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, you can use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
## Persistence
@@ -430,7 +430,7 @@ Regular upgrade is compatible from previous versions.
### To 6.2.0
This version introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/master/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
This version introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/main/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
### To 6.0.0
bitnami/kibana/values.yaml
+1 -1
View File
@@ -643,7 +643,7 @@ metrics:
##
metricRelabelings: []
## @param metrics.serviceMonitor.selector Prometheus instance selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
## e.g:
## selector:
## prometheus: my-prometheus
bitnami/kong/Chart.yaml
+1 -1
View File
@@ -18,7 +18,7 @@ dependencies:
version: 9.x.x
description: Kong is an open source Microservice API gateway and platform designed for managing microservices requests of high-availability, fault-tolerance, and distributed systems.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/kong
home: https://github.com/bitnami/charts/tree/main/bitnami/kong
icon: https://bitnami.com/assets/stacks/kong/img/kong-stack-220x234.png
keywords:
- kong
bitnami/kong/README.md
+6 -6
View File
@@ -7,7 +7,7 @@ Kong is an open source Microservice API gateway and platform designed for managi
[Overview of Kong](https://konghq.com/kong-community-edition/)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```console
@@ -508,7 +508,7 @@ extraDeploy:
This chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod's affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.
## Troubleshooting
@@ -536,7 +536,7 @@ No issues are expected during the upgrade.
### To 5.0.0
The `cassandra` sub-chart was upgraded to `9.x.x`. Several values of the sub-chart were changed, so please check the [upgrade notes](https://github.com/bitnami/charts/tree/master/bitnami/cassandra#to-900).
The `cassandra` sub-chart was upgraded to `9.x.x`. Several values of the sub-chart were changed, so please check the [upgrade notes](https://github.com/bitnami/charts/tree/main/bitnami/cassandra#to-900).
No issues are expected during the upgrade.
@@ -609,7 +609,7 @@ postgresql 08:05:12.59 INFO ==> Deploying PostgreSQL with persisted data...
### To 4.0.0
This major updates the Cassandra subchart to its newest major, 4.0.0. [Here](https://github.com/bitnami/charts/tree/master/bitnami/cassandra#to-800) you can find more information about the changes introduced in those versions.
This major updates the Cassandra subchart to its newest major, 4.0.0. [Here](https://github.com/bitnami/charts/tree/main/bitnami/cassandra#to-800) you can find more information about the changes introduced in those versions.
### To 2.0.0
@@ -617,9 +617,9 @@ PostgreSQL and Cassandra dependencies versions were bumped to new major versions
In order to properly migrate your data to this new version:
* If you were using PostgreSQL as your database, please refer to the [PostgreSQL Upgrade Notes](https://github.com/bitnami/charts/tree/master/bitnami/postgresql#900).
* If you were using PostgreSQL as your database, please refer to the [PostgreSQL Upgrade Notes](https://github.com/bitnami/charts/tree/main/bitnami/postgresql#900).
* If you were using Cassandra as your database, please refer to the [Cassandra Upgrade Notes](https://github.com/bitnami/charts/tree/master/bitnami/cassandra#to-600).
* If you were using Cassandra as your database, please refer to the [Cassandra Upgrade Notes](https://github.com/bitnami/charts/tree/main/bitnami/cassandra#to-600).
## License
bitnami/kong/values.yaml
+3 -3
View File
@@ -757,7 +757,7 @@ migration:
##
## PostgreSQL chart configuration
## ref: https://github.com/bitnami/charts/blob/master/bitnami/postgresql/values.yaml
## ref: https://github.com/bitnami/charts/blob/main/bitnami/postgresql/values.yaml
## @param postgresql.enabled Switch to enable or disable the PostgreSQL helm chart
## @param postgresql.auth.postgresPassword Password for the "postgres" admin user
## @param postgresql.auth.username Name for a custom user to create
@@ -812,7 +812,7 @@ postgresql:
##
## Cassandra chart configuration
## ref: https://github.com/bitnami/charts/blob/master/bitnami/cassandra/values.yaml
## ref: https://github.com/bitnami/charts/blob/main/bitnami/cassandra/values.yaml
## @param cassandra.enabled Switch to enable or disable the Cassandra helm chart
## @param cassandra.dbUser.user Cassandra admin user
## @param cassandra.dbUser.password Password for `cassandra.dbUser.user`. Randomly generated if empty
@@ -902,7 +902,7 @@ metrics:
##
labels: {}
## @param metrics.serviceMonitor.selector Prometheus instance selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
selector: {}
## @param metrics.serviceMonitor.relabelings RelabelConfigs to apply to samples before scraping
bitnami/kube-prometheus/Chart.yaml
+1 -1
View File
@@ -18,7 +18,7 @@ dependencies:
version: 2.x.x
description: Prometheus Operator provides easy monitoring definitions for Kubernetes services and deployment and management of Prometheus instances.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/kube-prometheus
home: https://github.com/bitnami/charts/tree/main/bitnami/kube-prometheus
icon: https://bitnami.com/assets/stacks/prometheus-operator/img/prometheus-operator-stack-220x234.png
keywords:
- prometheus
bitnami/kube-prometheus/README.md
+5 -5
View File
@@ -7,7 +7,7 @@ Prometheus Operator provides easy monitoring definitions for Kubernetes services
[Overview of Prometheus Operator](https://github.com/coreos/prometheus-operator)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
```bash
@@ -749,7 +749,7 @@ Refer to the [chart documentation on customizing alert configurations](https://d
This chart allows setting custom Pod affinity using the `XXX.affinity` parameter(s). Find more information about Pod's affinity in the [Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/master/bitnami/common#affinities) chart. To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.nodeAffinityPreset` parameters.
As an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.nodeAffinityPreset` parameters.
## Troubleshooting
@@ -763,7 +763,7 @@ $ helm upgrade my-release my-repo/kube-prometheus
### To 8.0.0
This major updates the kube-state-metrics subchart to its newest major, 3.0.0, and the node-exporter subchart to its newest major, 3.0.0. Both releases contains name changes to a few of its values. For more information, please refer to [kube-state-metrics upgrade notes](https://github.com/bitnami/charts/tree/master/bitnami/kube-state-metrics#to-300) and [node-exporter upgrade notes](https://github.com/bitnami/charts/tree/master/bitnami/node-exporter#to-300).
This major updates the kube-state-metrics subchart to its newest major, 3.0.0, and the node-exporter subchart to its newest major, 3.0.0. Both releases contains name changes to a few of its values. For more information, please refer to [kube-state-metrics upgrade notes](https://github.com/bitnami/charts/tree/main/bitnami/kube-state-metrics#to-300) and [node-exporter upgrade notes](https://github.com/bitnami/charts/tree/main/bitnami/node-exporter#to-300).
### To 7.0.0
@@ -831,7 +831,7 @@ If you use [Strategic Merge Patch](https://github.com/prometheus-operator/promet
### To 5.0.0
This major updates the kube-state-metrics subchart to it newest major, 2.0.0, which contains name changes to a few of its values. For more information on this subchart's major, please refer to [kube-state-metrics upgrade notes](https://github.com/bitnami/charts/tree/master/bitnami/kube-state-metrics#to-200).
This major updates the kube-state-metrics subchart to it newest major, 2.0.0, which contains name changes to a few of its values. For more information on this subchart's major, please refer to [kube-state-metrics upgrade notes](https://github.com/bitnami/charts/tree/main/bitnami/kube-state-metrics#to-200).
### To 4.4.0
@@ -894,7 +894,7 @@ $ helm upgrade my-release --set prometheus.thanos.create=true my-repo/kube-prome
- The chart was renamed to `kube-prometheus` to be more accurate with the actual capabilities of the chart: it does not just deploy the Prometheus operator, it deploys an entire cluster monitoring stack, that includes other components (e.g. NodeExporter or Kube State metrics). Find more information about the reasons behind this decision at [#3490](https://github.com/bitnami/charts/issues/3490).
- New CRDs were added and some existing ones were updated.
- This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/master/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
- This version also introduces `bitnami/common`, a [library chart](https://helm.sh/docs/topics/library_charts/#helm) as a dependency. More documentation about this new utility could be found [here](https://github.com/bitnami/charts/tree/main/bitnami/common#bitnami-common-library-chart). Please, make sure that you have updated the chart dependencies before executing any upgrade.
> Note: There is no backwards compatibility due to the above mentioned changes. It's necessary to install a new release of the chart, and migrate the existing TSDB data to the new Prometheus instances.
bitnami/kube-prometheus/values.yaml
+1 -1
View File
@@ -1566,7 +1566,7 @@ alertmanager:
##
scrapeTimeout: ""
## @param alertmanager.serviceMonitor.selector ServiceMonitor selector labels
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
## ref: https://github.com/bitnami/charts/tree/main/bitnami/prometheus-operator#prometheus-configuration
##
## selector:
## prometheus: my-prometheus
bitnami/kube-state-metrics/Chart.yaml
+1 -1
View File
@@ -10,7 +10,7 @@ dependencies:
version: 2.x.x
description: kube-state-metrics is a simple service that listens to the Kubernetes API server and generates metrics about the state of the objects.
engine: gotpl
home: https://github.com/bitnami/charts/tree/master/bitnami/kube-state-metrics
home: https://github.com/bitnami/charts/tree/main/bitnami/kube-state-metrics
icon: https://bitnami.com/assets/stacks/kube-state-metrics/img/kube-state-metrics-stack-220x234.png
keywords:
- prometheus

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