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/*] Fix typo in comments (relay -> rely) (#10151)

Browse Source 
* [bitnami/*] Fix typo in comments (relay -> rely)

Signed-off-by: Carlos Rodriguez Hernandez <carlosrh@vmware.com>

* [skip ci] Update README.md with readme-generator-for-helm

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

Co-authored-by: Bitnami Containers <containers@bitnami.com>
This commit is contained in:
Carlos Rodríguez Hernández
2022-05-11 19:07:46 +02:00
committed by GitHub
co-authored by Bitnami Containers
parent fa19a55181
commit 9cfe4a48cc
67 changed files with 255 additions and 242 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/airflow/README.md
+6 -6
View File
@@ -91,7 +91,7 @@ The command removes all the Kubernetes components associated with the chart and
| `dags.existingConfigmap` | Name of an existing ConfigMap with all the DAGs files you want to load in Airflow | `""` |
| `dags.image.registry` | Init container load-dags image registry | `docker.io` |
| `dags.image.repository` | Init container load-dags image repository | `bitnami/bitnami-shell` |
| `dags.image.tag` | Init container load-dags image tag (immutable tags are recommended) | `10-debian-10-r400` |
| `dags.image.tag` | Init container load-dags image tag (immutable tags are recommended) | `10-debian-10-r402` |
| `dags.image.pullPolicy` | Init container load-dags image pull policy | `IfNotPresent` |
| `dags.image.pullSecrets` | Init container load-dags image pull secrets | `[]` |
| `extraEnvVars` | Add extra environment variables for all the Airflow pods | `[]` |
@@ -110,7 +110,7 @@ The command removes all the Kubernetes components associated with the chart and
| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | --------------------- |
| `web.image.registry` | Airflow image registry | `docker.io` |
| `web.image.repository` | Airflow image repository | `bitnami/airflow` |
| `web.image.tag` | Airflow image tag (immutable tags are recommended) | `2.2.5-debian-10-r14` |
| `web.image.tag` | Airflow image tag (immutable tags are recommended) | `2.2.5-debian-10-r16` |
| `web.image.pullPolicy` | Airflow image pull policy | `IfNotPresent` |
| `web.image.pullSecrets` | Airflow image pull secrets | `[]` |
| `web.image.debug` | Enable image debug mode | `false` |
@@ -185,7 +185,7 @@ The command removes all the Kubernetes components associated with the chart and
| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | --------------------------- |
| `scheduler.image.registry` | Airflow Scheduler image registry | `docker.io` |
| `scheduler.image.repository` | Airflow Scheduler image repository | `bitnami/airflow-scheduler` |
| `scheduler.image.tag` | Airflow Scheduler image tag (immutable tags are recommended) | `2.2.5-debian-10-r14` |
| `scheduler.image.tag` | Airflow Scheduler image tag (immutable tags are recommended) | `2.2.5-debian-10-r15` |
| `scheduler.image.pullPolicy` | Airflow Scheduler image pull policy | `IfNotPresent` |
| `scheduler.image.pullSecrets` | Airflow Scheduler image pull secrets | `[]` |
| `scheduler.image.debug` | Enable image debug mode | `false` |
@@ -239,7 +239,7 @@ The command removes all the Kubernetes components associated with the chart and
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | ------------------------ |
| `worker.image.registry` | Airflow Worker image registry | `docker.io` |
| `worker.image.repository` | Airflow Worker image repository | `bitnami/airflow-worker` |
| `worker.image.tag` | Airflow Worker image tag (immutable tags are recommended) | `2.2.5-debian-10-r14` |
| `worker.image.tag` | Airflow Worker image tag (immutable tags are recommended) | `2.2.5-debian-10-r15` |
| `worker.image.pullPolicy` | Airflow Worker image pull policy | `IfNotPresent` |
| `worker.image.pullSecrets` | Airflow Worker image pull secrets | `[]` |
| `worker.image.debug` | Enable image debug mode | `false` |
@@ -319,7 +319,7 @@ The command removes all the Kubernetes components associated with the chart and
| ------------------------------ | -------------------------------------------------------------------------------------- | --------------------- |
| `git.image.registry` | Git image registry | `docker.io` |
| `git.image.repository` | Git image repository | `bitnami/git` |
| `git.image.tag` | Git image tag (immutable tags are recommended) | `2.36.0-debian-10-r1` |
| `git.image.tag` | Git image tag (immutable tags are recommended) | `2.36.0-debian-10-r3` |
| `git.image.pullPolicy` | Git image pull policy | `IfNotPresent` |
| `git.image.pullSecrets` | Git image pull secrets | `[]` |
| `git.dags.enabled` | Enable in order to download DAG files from git repositories. | `false` |
@@ -411,7 +411,7 @@ The command removes all the Kubernetes components associated with the chart and
| `metrics.enabled` | Whether or not to create a standalone Airflow exporter to expose Airflow metrics | `false` |
| `metrics.image.registry` | Airflow exporter image registry | `docker.io` |
| `metrics.image.repository` | Airflow exporter image repository | `bitnami/airflow-exporter` |
| `metrics.image.tag` | Airflow exporter image tag (immutable tags are recommended) | `0.20220314.0-debian-10-r37` |
| `metrics.image.tag` | Airflow exporter image tag (immutable tags are recommended) | `0.20220314.0-debian-10-r39` |
| `metrics.image.pullPolicy` | Airflow exporter image pull policy | `IfNotPresent` |
| `metrics.image.pullSecrets` | Airflow exporter image pull secrets | `[]` |
| `metrics.extraEnvVars` | Array with extra environment variables to add Airflow exporter pods | `[]` |
bitnami/airflow/values.yaml
+2 -2
View File
@@ -1143,8 +1143,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
##
tls: false
## @param ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
bitnami/argo-workflows/Chart.yaml
+1 -1
View File
@@ -35,4 +35,4 @@ sources:
- https://github.com/bitnami/bitnami-docker-argo-workflow-controller
- https://github.com/bitnami/bitnami-docker-argo-workflow-exec
- https://argoproj.github.io/workflows/
version: 1.1.13
version: 1.1.14
bitnami/argo-workflows/README.md
+4 -3
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.2.9-scratch-r0` |
| `server.image.tag` | server image tag (immutable tags are recommended) | `3.3.5-scratch-r0` |
| `server.image.pullPolicy` | server image pull policy | `Always` |
| `server.image.pullSecrets` | server image pull secrets | `[]` |
| `server.enabled` | Enable server deployment | `true` |
@@ -184,7 +184,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.2.9-scratch-r0` |
| `controller.image.tag` | controller image tag (immutable tags are recommended) | `3.3.5-scratch-r0` |
| `controller.image.pullPolicy` | controller image pull policy | `IfNotPresent` |
| `controller.image.pullSecrets` | controller image pull secrets | `[]` |
| `controller.replicaCount` | Number of controller replicas to deploy | `1` |
@@ -281,13 +281,14 @@ The command removes all the Kubernetes components associated with the chart and
| `controller.service.annotations` | Additional custom annotations for controller service | `{}` |
| `controller.service.extraPorts` | Extra port to expose on the controller service | `[]` |
### Executor configuration section
| Name | Description | Value |
| ---------------------------------------------------------- | ------------------------------------------------------------- | ---------------------------- |
| `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.2.8-debian-10-r24` |
| `executor.image.tag` | executor image tag (immutable tags are recommended) | `3.3.4-debian-10-r4` |
| `executor.image.pullPolicy` | executor image pull policy | `Always` |
| `executor.image.pullSecrets` | executor image pull secrets | `[]` |
| `executor.resources.limits` | The resources limits for the init container | `{}` |
bitnami/argo-workflows/values.yaml
+2 -2
View File
@@ -1040,8 +1040,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
##
tls: false
## DEPRECATED: Use ingress.annotations instead of ingress.certManager
bitnami/aspnet-core/README.md
+3 -3
View File
@@ -81,7 +81,7 @@ The command removes all the Kubernetes components associated with the chart and
| -------------------- | -------------------------------------------------------------------- | --------------------- |
| `image.registry` | ASP.NET Core image registry | `docker.io` |
| `image.repository` | ASP.NET Core image repository | `bitnami/aspnet-core` |
| `image.tag` | ASP.NET Core image tag (immutable tags are recommended) | `6.0.1-debian-10-r30` |
| `image.tag` | ASP.NET Core image tag (immutable tags are recommended) | `6.0.5-debian-10-r0` |
| `image.pullPolicy` | ASP.NET Core image pull policy | `IfNotPresent` |
| `image.pullSecrets` | ASP.NET Core image pull secrets | `[]` |
| `image.debug` | Enable image debug mode | `false` |
@@ -165,7 +165,7 @@ The command removes all the Kubernetes components associated with the chart and
| `appFromExternalRepo.enabled` | Enable to download/build ASP.NET Core app from external git repository | `true` |
| `appFromExternalRepo.clone.image.registry` | Git image registry | `docker.io` |
| `appFromExternalRepo.clone.image.repository` | Git image repository | `bitnami/git` |
| `appFromExternalRepo.clone.image.tag` | Git image tag (immutable tags are recommended) | `2.34.1-debian-10-r46` |
| `appFromExternalRepo.clone.image.tag` | Git image tag (immutable tags are recommended) | `2.36.1-debian-10-r4` |
| `appFromExternalRepo.clone.image.pullPolicy` | Git image pull policy | `IfNotPresent` |
| `appFromExternalRepo.clone.image.pullSecrets` | Git image pull secrets | `[]` |
| `appFromExternalRepo.clone.repository` | Git repository to clone | `https://github.com/dotnet/AspNetCore.Docs.git` |
@@ -173,7 +173,7 @@ The command removes all the Kubernetes components associated with the chart and
| `appFromExternalRepo.clone.extraVolumeMounts` | Add extra volume mounts for the GIT container | `[]` |
| `appFromExternalRepo.publish.image.registry` | .NET SDK image registry | `docker.io` |
| `appFromExternalRepo.publish.image.repository` | .NET SDK image repository | `bitnami/dotnet-sdk` |
| `appFromExternalRepo.publish.image.tag` | .NET SDK image tag (immutable tags are recommended) | `6.0.101-debian-10-r29` |
| `appFromExternalRepo.publish.image.tag` | .NET SDK image tag (immutable tags are recommended) | `6.0.202-debian-10-r29` |
| `appFromExternalRepo.publish.image.pullPolicy` | .NET SDK image pull policy | `IfNotPresent` |
| `appFromExternalRepo.publish.image.pullSecrets` | .NET SDK image pull secrets | `[]` |
| `appFromExternalRepo.publish.subFolder` | Sub folder under the Git repository containing the ASP.NET Core app | `aspnetcore/fundamentals/servers/kestrel/samples/6.x/KestrelSample` |
bitnami/aspnet-core/values.yaml
+3 -3
View File
@@ -520,7 +520,7 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Rely on cert-manager to create it by setting the corresponding annotations
##
tls: false
## @param ingress.extraPaths Any additional arbitrary paths that may need to be added to the ingress under the main host.
@@ -608,8 +608,8 @@ healthIngress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates
##
tls: false
## DEPRECATED: Use healthIngress.annotations instead of healthIngress.certManager
bitnami/concourse/README.md
+23 -20
View File
@@ -65,17 +65,18 @@ The command removes all the Kubernetes components associated with the chart and
### Common parameters
| Name | Description | Value |
| ------------------------ | --------------------------------------------------------------------------------------- | -------------- |
| `kubeVersion` | Override Kubernetes version | `""` |
| `nameOverride` | String to partially override common.names.fullname | `""` |
| `fullnameOverride` | String to fully override common.names.fullname | `""` |
| `commonLabels` | Labels to add to all deployed objects | `{}` |
| `commonAnnotations` | Annotations to add to all deployed objects | `{}` |
| `extraDeploy` | Array of extra objects to deploy with the release | `[]` |
| `diagnosticMode.enabled` | Enable diagnostic mode (all probes will be disabled and the command will be overridden) | `false` |
| `diagnosticMode.command` | Command to override all containers in the deployment(s)/statefulset(s) | `["sleep"]` |
| `diagnosticMode.args` | Args to override all containers in the deployment(s)/statefulset(s) | `["infinity"]` |
| Name | Description | Value |
| ------------------------ | --------------------------------------------------------------------------------------- | --------------- |
| `kubeVersion` | Override Kubernetes version | `""` |
| `nameOverride` | String to partially override common.names.fullname | `""` |
| `fullnameOverride` | String to fully override common.names.fullname | `""` |
| `clusterDomain` | Kubernetes Cluster Domain | `cluster.local` |
| `commonLabels` | Labels to add to all deployed objects | `{}` |
| `commonAnnotations` | Annotations to add to all deployed objects | `{}` |
| `extraDeploy` | Array of extra objects to deploy with the release | `[]` |
| `diagnosticMode.enabled` | Enable diagnostic mode (all probes will be disabled and the command will be overridden) | `false` |
| `diagnosticMode.command` | Command to override all containers in the deployment(s)/statefulset(s) | `["sleep"]` |
| `diagnosticMode.args` | Args to override all containers in the deployment(s)/statefulset(s) | `["infinity"]` |
### Common Concourse Parameters
@@ -84,7 +85,7 @@ The command removes all the Kubernetes components associated with the chart and
| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | --------------------- |
| `image.registry` | image registry | `docker.io` |
| `image.repository` | image repository | `bitnami/concourse` |
| `image.tag` | image tag (immutable tags are recommended) | `7.6.0-debian-10-r67` |
| `image.tag` | image tag (immutable tags are recommended) | `7.7.1-debian-10-r22` |
| `image.pullPolicy` | image pull policy | `IfNotPresent` |
| `image.pullSecrets` | image pull secrets | `[]` |
| `secrets.localAuth.enabled` | the use of local authentication (basic auth). | `true` |
@@ -191,7 +192,7 @@ The command removes all the Kubernetes components associated with the chart and
| `web.rbac.rules` | Custom RBAC rules to set | `[]` |
| `web.serviceAccount.create` | Specifies whether a ServiceAccount should be created | `true` |
| `web.serviceAccount.name` | Override Web service account name | `""` |
| `web.serviceAccount.automountServiceAccountToken` | Allows auto mount of ServiceAccountToken on the serviceAccount created | `false` |
| `web.serviceAccount.automountServiceAccountToken` | Allows auto mount of ServiceAccountToken on the serviceAccount created | `true` |
| `web.serviceAccount.annotations` | Additional custom annotations for the ServiceAccount | `{}` |
@@ -206,7 +207,7 @@ The command removes all the Kubernetes components associated with the chart and
| `worker.existingSecret` | name of an existing secret resource containing the keys and the pub | `""` |
| `worker.baggageclaim.logLevel` | Minimum level of logs to see. Allowed values: `debug`, `info`, and `error` | `info` |
| `worker.baggageclaim.bindIp` | IP address on which to listen for API traffic | `127.0.0.1` |
| `worker.baggageclaim.debugbindIp` | IP address on which to listen for the pprof debugger endpoints | `127.0.0.1` |
| `worker.baggageclaim.debugBindIp` | IP address on which to listen for the pprof debugger endpoints | `127.0.0.1` |
| `worker.baggageclaim.disableUserNamespaces` | Disable remapping of user/group IDs in unprivileged volumes | `""` |
| `worker.baggageclaim.volumes` | Directory in which to place volume data | `""` |
| `worker.baggageclaim.driver` | Driver to use for managing volumes. Allowed values: `detect`, `naive`, `btrfs`, and `overlay` | `""` |
@@ -216,7 +217,7 @@ The command removes all the Kubernetes components associated with the chart and
| `worker.command` | Override default container command (useful when using custom images) | `[]` |
| `worker.args` | Override worker default args | `[]` |
| `worker.replicaCount` | Number of worker replicas | `2` |
| `worker.mode` | Selects kind of Deployment. Valid Options are: statefulSet | deployment | `deployment` |
| `worker.mode` | Selects kind of Deployment. Allowed values: `deployment` or `statefulset` | `deployment` |
| `worker.containerPorts.garden` | Concourse worker Garden server container port | `7777` |
| `worker.containerPorts.health` | Concourse worker health-check container port | `8888` |
| `worker.containerPorts.baggageclaim` | Concourse worker baggageclaim API container port | `7788` |
@@ -264,6 +265,7 @@ The command removes all the Kubernetes components associated with the chart and
| `worker.priorityClassName` | Priority Class to use for each pod (Concourse worker) | `""` |
| `worker.schedulerName` | Use an alternate scheduler, e.g. "stork". | `""` |
| `worker.terminationGracePeriodSeconds` | Seconds Concourse worker pod needs to terminate gracefully | `""` |
| `worker.podManagementPolicy` | Statefulset Pod Management Policy Type. Allowed values: `OrderedReady` or `Parallel` | `OrderedReady` |
| `worker.updateStrategy.rollingUpdate` | Concourse worker statefulset rolling update configuration parameters | `{}` |
| `worker.updateStrategy.type` | Concourse worker statefulset strategy type | `RollingUpdate` |
| `worker.lifecycleHooks` | for the Concourse worker container(s) to automate configuration before or after startup | `{}` |
@@ -280,8 +282,8 @@ The command removes all the Kubernetes components associated with the chart and
| `worker.autoscaling.builtInMetrics` | Array with built-in metrics | `[]` |
| `worker.autoscaling.customMetrics` | Array with custom metrics | `[]` |
| `worker.pdb.create` | Create Pod disruption budget object for Concourse worker nodes | `true` |
| `worker.pdb.minAvailable` | Minimum number of Concourse workers available after an eviction | `2` |
| `worker.pdb.maxAvailable` | Maximum number of Concourse workers available | `""` |
| `worker.pdb.minAvailable` | Minimum number / percentage of Concourse worker pods that should remain scheduled | `2` |
| `worker.pdb.maxUnavailable` | Maximum number/percentage of Concourse worker pods that may be made unavailable | `""` |
| `worker.psp.create` | Whether to create a PodSecurityPolicy. WARNING: PodSecurityPolicy is deprecated in Kubernetes v1.21 or later, unavailable in v1.25 or later | `false` |
| `worker.persistence.enabled` | Enable Concourse worker data persistence using PVC | `true` |
| `worker.persistence.existingClaim` | Name of an existing PVC to use | `""` |
@@ -294,7 +296,7 @@ The command removes all the Kubernetes components associated with the chart and
| `worker.rbac.rules` | Custom RBAC rules to set | `[]` |
| `worker.serviceAccount.create` | Specifies whether a ServiceAccount should be created | `true` |
| `worker.serviceAccount.name` | Override worker service account name | `""` |
| `worker.serviceAccount.automountServiceAccountToken` | Allows auto mount of ServiceAccountToken on the serviceAccount created | `false` |
| `worker.serviceAccount.automountServiceAccountToken` | Allows auto mount of ServiceAccountToken on the serviceAccount created | `true` |
| `worker.serviceAccount.annotations` | Additional custom annotations for the ServiceAccount | `{}` |
@@ -325,9 +327,10 @@ The command removes all the Kubernetes components associated with the chart and
| `service.workerGateway.annotations` | Additional custom annotations for Concourse worker gateway service | `{}` |
| `service.workerGateway.extraPorts` | Extra port to expose on Concourse worker gateway service | `[]` |
| `ingress.enabled` | Enable ingress record generation for Concourse | `false` |
| `ingress.ingressClassName` | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+) | `""` |
| `ingress.pathType` | Ingress path type | `ImplementationSpecific` |
| `ingress.apiVersion` | Force Ingress API version (automatically detected if not set) | `""` |
| `ingress.hostname` | Default host for the ingress record | `Concourse.local` |
| `ingress.hostname` | Default host for the ingress record | `concourse.local` |
| `ingress.path` | Default path for the ingress record | `/` |
| `ingress.annotations` | Additional annotations for the Ingress resource. To enable certificate autogeneration, place here your cert-manager annotations. | `{}` |
| `ingress.tls` | Enable TLS configuration for the host defined at `ingress.hostname` parameter | `false` |
@@ -345,7 +348,7 @@ The command removes all the Kubernetes components associated with the chart and
| `volumePermissions.enabled` | Enable init container that changes the owner and group of the persistent volume | `false` |
| `volumePermissions.image.registry` | Init container volume-permissions image registry | `docker.io` |
| `volumePermissions.image.repository` | Init container volume-permissions image repository | `bitnami/bitnami-shell` |
| `volumePermissions.image.tag` | Init container volume-permissions image tag (immutable tags are recommended) | `10-debian-10-r326` |
| `volumePermissions.image.tag` | Init container volume-permissions image tag (immutable tags are recommended) | `10-debian-10-r402` |
| `volumePermissions.image.pullPolicy` | Init container volume-permissions image pull policy | `IfNotPresent` |
| `volumePermissions.image.pullSecrets` | Init container volume-permissions image pull secrets | `[]` |
| `volumePermissions.resources.limits` | Init container volume-permissions resource limits | `{}` |
bitnami/concourse/values.yaml
+2 -2
View File
@@ -1080,8 +1080,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
##
tls: false
## @param ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
bitnami/discourse/Chart.yaml
+1 -1
View File
@@ -35,4 +35,4 @@ sources:
- https://github.com/bitnami/bitnami-docker-discourse
- https://github.com/spinnaker
- https://www.discourse.org/
version: 7.0.16
version: 7.0.17
bitnami/discourse/README.md
+47 -47
View File
@@ -81,52 +81,52 @@ The command removes all the Kubernetes components associated with the chart and
### Discourse Common parameters
| Name | Description | Value |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | --------------------- |
| `image.registry` | Discourse image registry | `docker.io` |
| `image.repository` | Discourse image repository | `bitnami/discourse` |
| `image.tag` | Discourse image tag | `2.7.13-debian-10-r0` |
| `image.pullPolicy` | Discourse image pull policy | `IfNotPresent` |
| `image.pullSecrets` | Discourse image pull secrets | `[]` |
| `image.debug` | Enable image debug mode | `false` |
| `auth.email` | Discourse admin user email | `user@example.com` |
| `auth.username` | Discourse admin user | `user` |
| `auth.password` | Discourse admin password. WARNING: Minimum length of 10 characters | `""` |
| `auth.existingSecret` | Name of an existing secret to use for Discourse credentials | `""` |
| `host` | Hostname to create application URLs (include the port if =/= 80) | `""` |
| `siteName` | Discourse site name | `My Site!` |
| `smtp.enabled` | Enable/disable SMTP | `false` |
| `smtp.host` | SMTP host name | `""` |
| `smtp.port` | SMTP port number | `""` |
| `smtp.user` | SMTP account user name | `""` |
| `smtp.password` | SMTP account password | `""` |
| `smtp.protocol` | SMTP protocol (Allowed values: tls, ssl) | `""` |
| `smtp.auth` | SMTP authentication method | `""` |
| `smtp.existingSecret` | Name of an existing Kubernetes secret. The secret must have the following key configured: `smtp-password` | `""` |
| `replicaCount` | Number of Discourse & Sidekiq replicas | `1` |
| `podSecurityContext.enabled` | Enabled Discourse pods' Security Context | `false` |
| `podSecurityContext.fsGroup` | Set Discourse pod's Security Context fsGroup | `0` |
| `hostAliases` | Add deployment host aliases | `[]` |
| `podAnnotations` | Additional pod annotations | `{}` |
| `podLabels` | Additional pod labels | `{}` |
| `podAffinityPreset` | Pod affinity preset. Allowed values: soft, hard | `""` |
| `podAntiAffinityPreset` | Pod anti-affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `soft` |
| `nodeAffinityPreset.type` | Node affinity preset type. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `nodeAffinityPreset.key` | Node label key to match Ignored if `affinity` is set. | `""` |
| `nodeAffinityPreset.values` | Node label values to match. Ignored if `affinity` is set. | `[]` |
| `affinity` | Affinity for pod assignment | `{}` |
| `nodeSelector` | Node labels for pod assignment. | `{}` |
| `tolerations` | Tolerations for pod assignment. | `[]` |
| `topologySpreadConstraints` | Topology Spread Constraints for pod assignment spread across your cluster among failure-domains. Evaluated as a template | `{}` |
| `priorityClassName` | Priority Class Name | `""` |
| `schedulerName` | Use an alternate scheduler, e.g. "stork". | `""` |
| `terminationGracePeriodSeconds` | Seconds Discourse pod needs to terminate gracefully | `""` |
| `updateStrategy.type` | Discourse deployment strategy type | `RollingUpdate` |
| `updateStrategy.rollingUpdate` | Discourse deployment rolling update configuration parameters | `{}` |
| `sidecars` | Add additional sidecar containers to the Discourse pods | `[]` |
| `initContainers` | Add additional init containers to the Discourse pods | `[]` |
| `extraVolumeMounts` | Optionally specify extra list of additional volumeMounts for the Discourse pods | `[]` |
| `extraVolumes` | Optionally specify extra list of additional volumes for the Discourse pods | `[]` |
| Name | Description | Value |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | -------------------- |
| `image.registry` | Discourse image registry | `docker.io` |
| `image.repository` | Discourse image repository | `bitnami/discourse` |
| `image.tag` | Discourse image tag | `2.8.3-debian-10-r7` |
| `image.pullPolicy` | Discourse image pull policy | `IfNotPresent` |
| `image.pullSecrets` | Discourse image pull secrets | `[]` |
| `image.debug` | Enable image debug mode | `false` |
| `auth.email` | Discourse admin user email | `user@example.com` |
| `auth.username` | Discourse admin user | `user` |
| `auth.password` | Discourse admin password. WARNING: Minimum length of 10 characters | `""` |
| `auth.existingSecret` | Name of an existing secret to use for Discourse credentials | `""` |
| `host` | Hostname to create application URLs (include the port if =/= 80) | `""` |
| `siteName` | Discourse site name | `My Site!` |
| `smtp.enabled` | Enable/disable SMTP | `false` |
| `smtp.host` | SMTP host name | `""` |
| `smtp.port` | SMTP port number | `""` |
| `smtp.user` | SMTP account user name | `""` |
| `smtp.password` | SMTP account password | `""` |
| `smtp.protocol` | SMTP protocol (Allowed values: tls, ssl) | `""` |
| `smtp.auth` | SMTP authentication method | `""` |
| `smtp.existingSecret` | Name of an existing Kubernetes secret. The secret must have the following key configured: `smtp-password` | `""` |
| `replicaCount` | Number of Discourse & Sidekiq replicas | `1` |
| `podSecurityContext.enabled` | Enabled Discourse pods' Security Context | `false` |
| `podSecurityContext.fsGroup` | Set Discourse pod's Security Context fsGroup | `0` |
| `hostAliases` | Add deployment host aliases | `[]` |
| `podAnnotations` | Additional pod annotations | `{}` |
| `podLabels` | Additional pod labels | `{}` |
| `podAffinityPreset` | Pod affinity preset. Allowed values: soft, hard | `""` |
| `podAntiAffinityPreset` | Pod anti-affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `soft` |
| `nodeAffinityPreset.type` | Node affinity preset type. Ignored if `affinity` is set. Allowed values: `soft` or `hard` | `""` |
| `nodeAffinityPreset.key` | Node label key to match Ignored if `affinity` is set. | `""` |
| `nodeAffinityPreset.values` | Node label values to match. Ignored if `affinity` is set. | `[]` |
| `affinity` | Affinity for pod assignment | `{}` |
| `nodeSelector` | Node labels for pod assignment. | `{}` |
| `tolerations` | Tolerations for pod assignment. | `[]` |
| `topologySpreadConstraints` | Topology Spread Constraints for pod assignment spread across your cluster among failure-domains. Evaluated as a template | `{}` |
| `priorityClassName` | Priority Class Name | `""` |
| `schedulerName` | Use an alternate scheduler, e.g. "stork". | `""` |
| `terminationGracePeriodSeconds` | Seconds Discourse pod needs to terminate gracefully | `""` |
| `updateStrategy.type` | Discourse deployment strategy type | `RollingUpdate` |
| `updateStrategy.rollingUpdate` | Discourse deployment rolling update configuration parameters | `{}` |
| `sidecars` | Add additional sidecar containers to the Discourse pods | `[]` |
| `initContainers` | Add additional init containers to the Discourse pods | `[]` |
| `extraVolumeMounts` | Optionally specify extra list of additional volumeMounts for the Discourse pods | `[]` |
| `extraVolumes` | Optionally specify extra list of additional volumes for the Discourse pods | `[]` |
### Discourse container parameters
@@ -221,7 +221,7 @@ The command removes all the Kubernetes components associated with the chart and
| Name | Description | Value |
| ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | ------------------------ |
| `service.type` | Discourse service type | `ClusterIP` |
| `service.ports.http` | Discourse service HTTP port | `8080` |
| `service.ports.http` | Discourse service HTTP port | `80` |
| `service.nodePorts.http` | Node port for HTTP | `""` |
| `service.sessionAffinity` | Control where client requests go, to the same pod or round-robin | `None` |
| `service.clusterIP` | Discourse service Cluster IP | `""` |
bitnami/discourse/values.yaml
+2 -2
View File
@@ -569,8 +569,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
##
tls: false
## @param ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
bitnami/elasticsearch/Chart.yaml
+1 -1
View File
@@ -25,4 +25,4 @@ name: elasticsearch
sources:
- https://github.com/bitnami/bitnami-docker-elasticsearch
- https://www.elastic.co/products/elasticsearch
version: 18.0.1
version: 18.0.2
bitnami/elasticsearch/README.md
+5 -5
View File
@@ -108,7 +108,7 @@ $ helm delete --purge my-release
| `initContainers` | Add additional init containers to the all elasticsearch node pod(s) | `[]` |
| `image.registry` | Elasticsearch image registry | `docker.io` |
| `image.repository` | Elasticsearch image repository | `bitnami/elasticsearch` |
| `image.tag` | Elasticsearch image tag (immutable tags are recommended) | `8.1.3-debian-10-r0` |
| `image.tag` | Elasticsearch image tag (immutable tags are recommended) | `8.2.0-debian-10-r1` |
| `image.pullPolicy` | Elasticsearch image pull policy | `IfNotPresent` |
| `image.pullSecrets` | Elasticsearch image pull secrets | `[]` |
| `image.debug` | Enable Elasticsearch image debug mode | `false` |
@@ -524,7 +524,7 @@ $ helm delete --purge my-release
| `curator.jobLabels` | Annotations to add to the job | `{}` |
| `curator.image.registry` | Elasticsearch Curator image registry | `docker.io` |
| `curator.image.repository` | Elasticsearch Curator image repository | `bitnami/elasticsearch-curator` |
| `curator.image.tag` | Elasticsearch Curator image tag | `5.8.4-debian-10-r321` |
| `curator.image.tag` | Elasticsearch Curator image tag | `5.8.4-debian-10-r333` |
| `curator.image.pullPolicy` | Elasticsearch Curator image pull policy | `IfNotPresent` |
| `curator.image.pullSecrets` | Elasticsearch Curator image pull secrets | `[]` |
| `curator.cronjob.schedule` | Schedule for the CronJob | `0 1 * * *` |
@@ -587,7 +587,7 @@ $ helm delete --purge my-release
| `metrics.fullnameOverride` | String to fully override common.names.fullname | `""` |
| `metrics.image.registry` | Metrics exporter image registry | `docker.io` |
| `metrics.image.repository` | Metrics exporter image repository | `bitnami/elasticsearch-exporter` |
| `metrics.image.tag` | Metrics exporter image tag | `1.3.0-debian-10-r176` |
| `metrics.image.tag` | Metrics exporter image tag | `1.3.0-debian-10-r188` |
| `metrics.image.pullPolicy` | Metrics exporter image pull policy | `IfNotPresent` |
| `metrics.image.pullSecrets` | Metrics exporter image pull secrets | `[]` |
| `metrics.extraArgs` | Extra arguments to add to the default exporter command | `[]` |
@@ -664,7 +664,7 @@ $ helm delete --purge my-release
| `volumePermissions.enabled` | Enable init container that changes volume permissions in the data directory (for cases where the default k8s `runAsUser` and `fsUser` values do not work) | `false` |
| `volumePermissions.image.registry` | Init container volume-permissions image registry | `docker.io` |
| `volumePermissions.image.repository` | Init container volume-permissions image name | `bitnami/bitnami-shell` |
| `volumePermissions.image.tag` | Init container volume-permissions image tag | `10-debian-10-r360` |
| `volumePermissions.image.tag` | Init container volume-permissions image tag | `10-debian-10-r415` |
| `volumePermissions.image.pullPolicy` | Init container volume-permissions image pull policy | `IfNotPresent` |
| `volumePermissions.image.pullSecrets` | Init container volume-permissions image pull secrets | `[]` |
| `volumePermissions.resources.limits` | The resources limits for the container | `{}` |
@@ -672,7 +672,7 @@ $ helm delete --purge my-release
| `sysctlImage.enabled` | Enable kernel settings modifier image | `true` |
| `sysctlImage.registry` | Kernel settings modifier image registry | `docker.io` |
| `sysctlImage.repository` | Kernel settings modifier image repository | `bitnami/bitnami-shell` |
| `sysctlImage.tag` | Kernel settings modifier image tag | `10-debian-10-r403` |
| `sysctlImage.tag` | Kernel settings modifier image tag | `10-debian-10-r415` |
| `sysctlImage.pullPolicy` | Kernel settings modifier image pull policy | `IfNotPresent` |
| `sysctlImage.pullSecrets` | Kernel settings modifier image pull secrets | `[]` |
| `sysctlImage.resources.limits` | The resources limits for the container | `{}` |
bitnami/elasticsearch/values.yaml
+4 -4
View File
@@ -370,8 +370,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
##
tls: false
## @param ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
@@ -1613,8 +1613,8 @@ ingest:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
##
tls: false
## @param ingest.ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
bitnami/geode/Chart.yaml
+1 -1
View File
@@ -22,4 +22,4 @@ name: geode
sources:
- https://github.com/bitnami/bitnami-docker-geode
- https://github.com/apache/geode
version: 0.4.19
version: 0.4.20
bitnami/geode/README.md
+12 -12
View File
@@ -54,7 +54,7 @@ The command removes all the Kubernetes components associated with the chart and
### Global parameters
| Name | Description | Value |
|:--------------------------|:------------------------------------------------|:------|
| ------------------------- | ----------------------------------------------- | ----- |
| `global.imageRegistry` | Global Docker image registry | `""` |
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` |
| `global.storageClass` | Global StorageClass for Persistent Volume(s) | `""` |
@@ -63,7 +63,7 @@ The command removes all the Kubernetes components associated with the chart and
### Common parameters
| Name | Description | Value |
|:-------------------------|:----------------------------------------------------------------------------------------|:----------------|
| ------------------------ | --------------------------------------------------------------------------------------- | --------------- |
| `kubeVersion` | Override Kubernetes version | `""` |
| `nameOverride` | String to partially override common.names.fullname | `""` |
| `fullnameOverride` | String to fully override common.names.fullname | `""` |
@@ -79,10 +79,10 @@ The command removes all the Kubernetes components associated with the chart and
### Apache Geode Common parameters
| Name | Description | Value |
|:-----------------------------------------|:---------------------------------------------------------------------------------------|:------------------------------------------------------------|
| ---------------------------------------- | -------------------------------------------------------------------------------------- | ----------------------------------------------------------- |
| `image.registry` | Apache Geode image registry | `docker.io` |
| `image.repository` | Apache Geode image repository | `bitnami/geode` |
| `image.tag` | Apache Geode image tag (immutable tags are recommended) | `1.14.2-debian-10-r23` |
| `image.tag` | Apache Geode image tag (immutable tags are recommended) | `1.14.4-debian-10-r21` |
| `image.pullPolicy` | Apache Geode image pull policy | `IfNotPresent` |
| `image.pullSecrets` | Apache Geode image pull secrets | `[]` |
| `image.debug` | Enable Apache Geode image debug mode | `false` |
@@ -104,7 +104,7 @@ The command removes all the Kubernetes components associated with the chart and
### Apache Geode Locator parameters
| Name | Description | Value |
|:------------------------------------------------|:------------------------------------------------------------------------------------------------------------|:--------------------|
| ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | ------------------- |
| `locator.logLevel` | Log level for Locator nodes | `info` |
| `locator.initialHeapSize` | Initial size of the heap on Locator nodes | `""` |
| `locator.maxHeapSize` | Maximum size of the heap on Locator nodes | `""` |
@@ -196,7 +196,7 @@ The command removes all the Kubernetes components associated with the chart and
### Apache Geode Cache Server parameters
| Name | Description | Value |
|:-------------------------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------|:--------------------|
| ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- |
| `server.logLevel` | Log level for Cache Server nodes | `info` |
| `server.initialHeapSize` | Initial size of the heap on Cache Server nodes | `""` |
| `server.maxHeapSize` | Maximum size of the heap on Cache Server nodes | `""` |
@@ -280,7 +280,7 @@ The command removes all the Kubernetes components associated with the chart and
### Traffic Exposure Parameters
| Name | Description | Value |
|:----------------------|:---------------------------------------------------------------------------------------------------------------------------------|:-------------------------|
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------- | ------------------------ |
| `ingress.enabled` | Enable ingress record generation for Apache Geode | `false` |
| `ingress.pathType` | Ingress path type | `ImplementationSpecific` |
| `ingress.apiVersion` | Force Ingress API version (automatically detected if not set) | `""` |
@@ -298,11 +298,11 @@ The command removes all the Kubernetes components associated with the chart and
### Init Container Parameters
| Name | Description | Value |
|:-------------------------------------------------------|:------------------------------------------------------------------------------------------------|:------------------------|
| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------- | ----------------------- |
| `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) | `10-debian-10-r305` |
| `volumePermissions.image.tag` | Bitnami Shell image tag (immutable tags are recommended) | `10-debian-10-r401` |
| `volumePermissions.image.pullPolicy` | Bitnami Shell image pull policy | `IfNotPresent` |
| `volumePermissions.image.pullSecrets` | Bitnami Shell image pull secrets | `[]` |
| `volumePermissions.resources.limits` | The resources limits for the init container | `{}` |
@@ -313,11 +313,11 @@ The command removes all the Kubernetes components associated with the chart and
### Metrics parameters
| Name | Description | Value |
|:------------------------------------------------|:---------------------------------------------------------------------------------|:----------------------|
| ----------------------------------------------- | -------------------------------------------------------------------------------- | --------------------- |
| `metrics.enabled` | Expose Apache Geode metrics | `false` |
| `metrics.image.registry` | Bitnami HAProxy image registry | `docker.io` |
| `metrics.image.repository` | Bitnami HAProxy image repository | `bitnami/haproxy` |
| `metrics.image.tag` | Bitnami HAProxy image tag (immutable tags are recommended) | `2.5.0-debian-10-r45` |
| `metrics.image.tag` | Bitnami HAProxy image tag (immutable tags are recommended) | `2.5.5-debian-10-r35` |
| `metrics.image.pullPolicy` | Bitnami HAProxy image pull policy | `IfNotPresent` |
| `metrics.image.pullSecrets` | Bitnami HAProxy image pull secrets | `[]` |
| `metrics.containerPort` | Metrics container port | `9914` |
@@ -354,7 +354,7 @@ The command removes all the Kubernetes components associated with the chart and
### Other Parameters
| Name | Description | Value |
|:----------------------------------------------|:-----------------------------------------------------------------------|:--------|
| --------------------------------------------- | ---------------------------------------------------------------------- | ------- |
| `serviceAccount.create` | Specifies whether a ServiceAccount should be created | `true` |
| `serviceAccount.name` | The name of the ServiceAccount to use. | `""` |
| `serviceAccount.automountServiceAccountToken` | Allows auto mount of ServiceAccountToken on the serviceAccount created | `false` |
bitnami/geode/values.yaml
+2 -2
View File
@@ -825,8 +825,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
##
tls: false
## @param ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
bitnami/ghost/Chart.yaml
+1 -1
View File
@@ -33,4 +33,4 @@ name: ghost
sources:
- https://github.com/bitnami/bitnami-docker-ghost
- https://www.ghost.org/
version: 17.0.6
version: 17.0.7
bitnami/ghost/README.md
+11 -2
View File
@@ -62,6 +62,7 @@ The command removes all the Kubernetes components associated with the chart and
| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` |
| `global.storageClass` | Global StorageClass for Persistent Volume(s) | `""` |
### Common parameters
| Name | Description | Value |
@@ -74,17 +75,19 @@ The command removes all the Kubernetes components associated with the chart and
| `clusterDomain` | Kubernetes cluster domain name | `cluster.local` |
| `extraDeploy` | Array of extra objects to deploy with the release | `[]` |
### Ghost Image parameters
| Name | Description | Value |
| ------------------- | ------------------------------------------------ | --------------------- |
| `image.registry` | Ghost image registry | `docker.io` |
| `image.repository` | Ghost image repository | `bitnami/ghost` |
| `image.tag` | Ghost image tag (immutable tags are recommended) | `4.41.1-debian-10-r0` |
| `image.tag` | Ghost image tag (immutable tags are recommended) | `4.47.0-debian-10-r0` |
| `image.pullPolicy` | Ghost image pull policy | `IfNotPresent` |
| `image.pullSecrets` | Ghost image pull secrets | `[]` |
| `image.debug` | Enable image debug mode | `false` |
### Ghost Configuration parameters
| Name | Description | Value |
@@ -112,6 +115,7 @@ The command removes all the Kubernetes components associated with the chart and
| `extraEnvVarsCM` | Name of existing ConfigMap containing extra env vars | `""` |
| `extraEnvVarsSecret` | Name of existing Secret containing extra env vars | `""` |
### Ghost deployment parameters
| Name | Description | Value |
@@ -167,6 +171,7 @@ The command removes all the Kubernetes components associated with the chart and
| `customLivenessProbe` | Custom livenessProbe that overrides the default one | `{}` |
| `customReadinessProbe` | Custom readinessProbe that overrides the default one | `{}` |
### Traffic Exposure Parameters
| Name | Description | Value |
@@ -198,6 +203,7 @@ The command removes all the Kubernetes components associated with the chart and
| `ingress.secrets` | Custom TLS certificates as secrets | `[]` |
| `ingress.ingressClassName` | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+) | `""` |
### Persistence Parameters
| Name | Description | Value |
@@ -212,13 +218,14 @@ 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) | `10-debian-10-r374` |
| `volumePermissions.image.tag` | Bitnami Shell image tag (immutable tags are recommended) | `10-debian-10-r415` |
| `volumePermissions.image.pullPolicy` | Bitnami Shell image pull policy | `IfNotPresent` |
| `volumePermissions.image.pullSecrets` | Bitnami Shell image pull secrets | `[]` |
| `volumePermissions.resources.limits` | The resources limits for the init container | `{}` |
| `volumePermissions.resources.requests` | The requested resources for the init container | `{}` |
| `volumePermissions.securityContext.runAsUser` | Set init container's Security Context runAsUser | `0` |
### Database Parameters
| Name | Description | Value |
@@ -243,6 +250,7 @@ The command removes all the Kubernetes components associated with the chart and
| `externalDatabase.ssl` | External Database ssl | `false` |
| `externalDatabase.sslCaFile` | External Database ssl CA filepath | `""` |
### NetworkPolicy parameters
| Name | Description | Value |
@@ -261,6 +269,7 @@ The command removes all the Kubernetes components associated with the chart and
| `networkPolicy.egressRules.customRules` | Custom network policy rule | `{}` |
| `serviceAccount.name` | Service Account Name | `""` |
The above parameters map to the env variables defined in [bitnami/ghost](https://github.com/bitnami/bitnami-docker-ghost). For more information please refer to the [bitnami/ghost](https://github.com/bitnami/bitnami-docker-ghost) image documentation.
> **Note**:
bitnami/ghost/values.yaml
+2 -2
View File
@@ -439,8 +439,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
##
tls: false
## DEPRECATED: Use ingress.annotations instead of ingress.certManager
bitnami/harbor/Chart.yaml
+1 -1
View File
@@ -34,4 +34,4 @@ sources:
- https://github.com/bitnami/bitnami-docker-harbor-registry
- https://github.com/bitnami/bitnami-docker-harbor-registryctl
- https://goharbor.io/
version: 12.3.6
version: 12.3.7
bitnami/harbor/README.md
+15 -15
View File
@@ -245,7 +245,7 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
| `volumePermissions.enabled` | Enable init container that changes the owner and group of the persistent volume | `false` |
| `volumePermissions.image.registry` | Init container volume-permissions image registry | `docker.io` |
| `volumePermissions.image.repository` | Init container volume-permissions image repository | `bitnami/bitnami-shell` |
| `volumePermissions.image.tag` | Init container volume-permissions image tag (immutable tags are recommended) | `10-debian-10-r399` |
| `volumePermissions.image.tag` | Init container volume-permissions image tag (immutable tags are recommended) | `10-debian-10-r411` |
| `volumePermissions.image.pullPolicy` | Init container volume-permissions image pull policy | `IfNotPresent` |
| `volumePermissions.image.pullSecrets` | Init container volume-permissions image pull secrets | `[]` |
| `volumePermissions.resources.limits` | Init container volume-permissions resource limits | `{}` |
@@ -260,7 +260,7 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | ---------------------- |
| `nginx.image.registry` | NGINX image registry | `docker.io` |
| `nginx.image.repository` | NGINX image repository | `bitnami/nginx` |
| `nginx.image.tag` | NGINX image tag (immutable tags are recommended) | `1.21.6-debian-10-r79` |
| `nginx.image.tag` | NGINX image tag (immutable tags are recommended) | `1.21.6-debian-10-r93` |
| `nginx.image.pullPolicy` | NGINX image pull policy | `IfNotPresent` |
| `nginx.image.pullSecrets` | NGINX image pull secrets | `[]` |
| `nginx.image.debug` | Enable NGINX image debug mode | `false` |
@@ -333,7 +333,7 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | ----------------------- |
| `portal.image.registry` | Harbor Portal image registry | `docker.io` |
| `portal.image.repository` | Harbor Portal image repository | `bitnami/harbor-portal` |
| `portal.image.tag` | Harbor Portal image tag (immutable tags are recommended) | `2.5.0-debian-10-r8` |
| `portal.image.tag` | Harbor Portal image tag (immutable tags are recommended) | `2.5.0-debian-10-r21` |
| `portal.image.pullPolicy` | Harbor Portal image pull policy | `IfNotPresent` |
| `portal.image.pullSecrets` | Harbor Portal image pull secrets | `[]` |
| `portal.image.debug` | Enable Harbor Portal image debug mode | `false` |
@@ -405,7 +405,7 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
| -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- |
| `core.image.registry` | Harbor Core image registry | `docker.io` |
| `core.image.repository` | Harbor Core image repository | `bitnami/harbor-core` |
| `core.image.tag` | Harbor Core image tag (immutable tags are recommended) | `2.5.0-debian-10-r8` |
| `core.image.tag` | Harbor Core image tag (immutable tags are recommended) | `2.5.0-debian-10-r19` |
| `core.image.pullPolicy` | Harbor Core image pull policy | `IfNotPresent` |
| `core.image.pullSecrets` | Harbor Core image pull secrets | `[]` |
| `core.image.debug` | Enable Harbor Core image debug mode | `false` |
@@ -487,7 +487,7 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
| -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------ |
| `jobservice.image.registry` | Harbor Jobservice image registry | `docker.io` |
| `jobservice.image.repository` | Harbor Jobservice image repository | `bitnami/harbor-jobservice` |
| `jobservice.image.tag` | Harbor Jobservice image tag (immutable tags are recommended) | `2.4.2-debian-10-r30` |
| `jobservice.image.tag` | Harbor Jobservice image tag (immutable tags are recommended) | `2.5.0-debian-10-r11` |
| `jobservice.image.pullPolicy` | Harbor Jobservice image pull policy | `IfNotPresent` |
| `jobservice.image.pullSecrets` | Harbor Jobservice image pull secrets | `[]` |
| `jobservice.image.debug` | Enable Harbor Jobservice image debug mode | `false` |
@@ -600,7 +600,7 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
| `registry.automountServiceAccountToken` | Automount service account token | `false` |
| `registry.server.image.registry` | Harbor Registry image registry | `docker.io` |
| `registry.server.image.repository` | Harbor Registry image repository | `bitnami/harbor-registry` |
| `registry.server.image.tag` | Harbor Registry image tag (immutable tags are recommended) | `2.5.0-debian-10-r7` |
| `registry.server.image.tag` | Harbor Registry image tag (immutable tags are recommended) | `2.5.0-debian-10-r19` |
| `registry.server.image.pullPolicy` | Harbor Registry image pull policy | `IfNotPresent` |
| `registry.server.image.pullSecrets` | Harbor Registry image pull secrets | `[]` |
| `registry.server.image.debug` | Enable Harbor Registry image debug mode | `false` |
@@ -646,7 +646,7 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
| `registry.server.service.ports.metrics` | Harbor Registry metrics service port | `8001` |
| `registry.controller.image.registry` | Harbor Registryctl image registry | `docker.io` |
| `registry.controller.image.repository` | Harbor Registryctl image repository | `bitnami/harbor-registryctl` |
| `registry.controller.image.tag` | Harbor Registryctl image tag (immutable tags are recommended) | `2.5.0-debian-10-r8` |
| `registry.controller.image.tag` | Harbor Registryctl image tag (immutable tags are recommended) | `2.5.0-debian-10-r19` |
| `registry.controller.image.pullPolicy` | Harbor Registryctl image pull policy | `IfNotPresent` |
| `registry.controller.image.pullSecrets` | Harbor Registryctl image pull secrets | `[]` |
| `registry.controller.image.debug` | Enable Harbor Registryctl image debug mode | `false` |
@@ -695,7 +695,7 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
| --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | ---------------------- |
| `chartmuseum.image.registry` | ChartMuseum image registry | `docker.io` |
| `chartmuseum.image.repository` | ChartMuseum image repository | `bitnami/chartmuseum` |
| `chartmuseum.image.tag` | ChartMuseum image tag (immutable tags are recommended) | `0.14.0-debian-10-r74` |
| `chartmuseum.image.tag` | ChartMuseum image tag (immutable tags are recommended) | `0.14.0-debian-10-r86` |
| `chartmuseum.image.pullPolicy` | ChartMuseum image pull policy | `IfNotPresent` |
| `chartmuseum.image.pullSecrets` | ChartMuseum image pull secrets | `[]` |
| `chartmuseum.image.debug` | Enable ChartMuseum image debug mode | `false` |
@@ -812,7 +812,7 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
| `clair.automountServiceAccountToken` | Automount service account token | `false` |
| `clair.adapter.image.registry` | Harbor Adapter for Clair image registry | `docker.io` |
| `clair.adapter.image.repository` | Harbor Adapter for Clair image repository | `bitnami/harbor-adapter-clair` |
| `clair.adapter.image.tag` | Harbor Adapter for Clair image tag (immutable tags are recommended) | `2.5.0-debian-10-r7` |
| `clair.adapter.image.tag` | Harbor Adapter for Clair image tag (immutable tags are recommended) | `2.5.0-debian-10-r18` |
| `clair.adapter.image.pullPolicy` | Harbor Adapter for Clair image pull policy | `IfNotPresent` |
| `clair.adapter.image.pullSecrets` | Harbor Adapter for Clair image pull secrets | `[]` |
| `clair.adapter.image.debug` | Enable Harbor Adapter for Clair image debug mode | `false` |
@@ -855,7 +855,7 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
| `clair.adapter.service.ports.https` | Harbor Adapter for Clair HTTPS service port | `8443` |
| `clair.server.image.registry` | Harbor Clair image registry | `docker.io` |
| `clair.server.image.repository` | Harbor Clair image repository | `bitnami/harbor-clair` |
| `clair.server.image.tag` | Harbor Clair image tag (immutable tags are recommended) | `2.5.0-debian-10-r7` |
| `clair.server.image.tag` | Harbor Clair image tag (immutable tags are recommended) | `2.5.0-debian-10-r19` |
| `clair.server.image.pullPolicy` | Harbor Clair image pull policy | `IfNotPresent` |
| `clair.server.image.pullSecrets` | Harbor Clair image pull secrets | `[]` |
| `clair.server.image.debug` | Enable Harbor Clair image debug mode | `false` |
@@ -906,7 +906,7 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
| `notary.secretName` | Fill the name of a kubernetes secret if you want to use your own TLS certificate authority, certificate and private key for notary communications. The secret must contain keys named `notary-signer-ca.crt`, `notary-signer.key` and `notary-signer.crt` that contain the CA, certificate and private key. They will be generated if not set. | `""` |
| `notary.server.image.registry` | Harbor Notary Server image registry | `docker.io` |
| `notary.server.image.repository` | Harbor Notary Server image repository | `bitnami/harbor-notary-server` |
| `notary.server.image.tag` | Harbor Notary Server image tag (immutable tags are recommended) | `2.5.0-debian-10-r8` |
| `notary.server.image.tag` | Harbor Notary Server image tag (immutable tags are recommended) | `2.5.0-debian-10-r19` |
| `notary.server.image.pullPolicy` | Harbor Notary Server image pull policy | `IfNotPresent` |
| `notary.server.image.pullSecrets` | Harbor Notary Server image pull secrets | `[]` |
| `notary.server.image.debug` | Enable Harbor Notary Server image debug mode | `false` |
@@ -968,7 +968,7 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
| `notary.server.automountServiceAccountToken` | Automount service account token | `false` |
| `notary.signer.image.registry` | Harbor Notary Signer image registry | `docker.io` |
| `notary.signer.image.repository` | Harbor Notary Signer image repository | `bitnami/harbor-notary-signer` |
| `notary.signer.image.tag` | Harbor Notary Signer image tag (immutable tags are recommended) | `2.5.0-debian-10-r7` |
| `notary.signer.image.tag` | Harbor Notary Signer image tag (immutable tags are recommended) | `2.5.0-debian-10-r19` |
| `notary.signer.image.pullPolicy` | Harbor Notary Signer image pull policy | `IfNotPresent` |
| `notary.signer.image.pullSecrets` | Harbor Notary Signer image pull secrets | `[]` |
| `notary.signer.image.debug` | Enable Harbor Notary Signer image debug mode | `false` |
@@ -1038,7 +1038,7 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | -------------------------------------- |
| `trivy.image.registry` | Harbor Adapter Trivy image registry | `docker.io` |
| `trivy.image.repository` | Harbor Adapter Trivy image repository | `bitnami/harbor-adapter-trivy` |
| `trivy.image.tag` | Harbor Adapter Trivy image tag (immutable tags are recommended) | `2.5.0-debian-10-r8` |
| `trivy.image.tag` | Harbor Adapter Trivy image tag (immutable tags are recommended) | `2.5.0-debian-10-r20` |
| `trivy.image.pullPolicy` | Harbor Adapter Trivy image pull policy | `IfNotPresent` |
| `trivy.image.pullSecrets` | Harbor Adapter Trivy image pull secrets | `[]` |
| `trivy.image.debug` | Enable Harbor Adapter Trivy image debug mode | `false` |
@@ -1119,7 +1119,7 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
| ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------- |
| `exporter.image.registry` | Registry for exporter image | `docker.io` |
| `exporter.image.repository` | Repository for exporter image | `bitnami/harbor-exporter` |
| `exporter.image.tag` | Tag for exporter image | `2.5.0-debian-10-r8` |
| `exporter.image.tag` | Tag for exporter image | `2.5.0-debian-10-r19` |
| `exporter.image.pullPolicy` | Harbor exporter image pull policy | `IfNotPresent` |
| `exporter.image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |
| `exporter.image.debug` | Specify if debug logs should be enabled | `false` |
@@ -1195,7 +1195,7 @@ Additionally, if `persistence.resourcePolicy` is set to `keep`, you should manua
| `postgresql.primary.initdb.scripts` | Initdb scripts to create Harbor databases | `{}` |
| `postgresql.image.registry` | PostgreSQL image registry | `docker.io` |
| `postgresql.image.repository` | PostgreSQL image repository | `bitnami/postgresql` |
| `postgresql.image.tag` | PostgreSQL image tag (immutable tags are recommended) | `11.15.0-debian-10-r67` |
| `postgresql.image.tag` | PostgreSQL image tag (immutable tags are recommended) | `11.15.0-debian-10-r80` |
| `externalDatabase.host` | Database host | `localhost` |
| `externalDatabase.port` | Database port number | `5432` |
| `externalDatabase.user` | Non-root username for Harbor | `bn_harbor` |
bitnami/harbor/values.yaml
+4 -4
View File
@@ -229,8 +229,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.core.hostname }}`
## You can:
## - Use the `ingress.core.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.core.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.core.selfSigned=true`
##
tls: false
## @param ingress.core.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
@@ -322,8 +322,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.notary.hostname }}`
## You can:
## - Use the `ingress.notary.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.notary.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.notary.selfSigned=true`
##
tls: false
## @param ingress.notary.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
bitnami/jenkins/README.md
+2 -2
View File
@@ -84,7 +84,7 @@ The command removes all the Kubernetes components associated with the chart and
| ------------------- | -------------------------------------------------- | ----------------------- |
| `image.registry` | Jenkins image registry | `docker.io` |
| `image.repository` | Jenkins image repository | `bitnami/jenkins` |
| `image.tag` | Jenkins image tag (immutable tags are recommended) | `2.332.1-debian-10-r16` |
| `image.tag` | Jenkins image tag (immutable tags are recommended) | `2.332.2-debian-10-r26` |
| `image.pullPolicy` | Jenkins image pull policy | `IfNotPresent` |
| `image.pullSecrets` | Jenkins image pull secrets | `[]` |
| `image.debug` | Enable image debug mode | `false` |
@@ -207,7 +207,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) | `10-debian-10-r379` |
| `volumePermissions.image.tag` | Bitnami Shell image tag (immutable tags are recommended) | `10-debian-10-r422` |
| `volumePermissions.image.pullPolicy` | Bitnami Shell image pull policy | `IfNotPresent` |
| `volumePermissions.image.pullSecrets` | Bitnami Shell image pull secrets | `[]` |
| `volumePermissions.resources.limits` | The resources limits for the init container | `{}` |
bitnami/jenkins/values.yaml
+2 -2
View File
@@ -412,8 +412,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
##
tls: false
## DEPRECATED: Use ingress.annotations instead of ingress.certManager
bitnami/jupyterhub/Chart.yaml
+1 -1
View File
@@ -26,4 +26,4 @@ name: jupyterhub
sources:
- https://github.com/bitnami/bitnami-docker-jupyterhub
- https://github.com/jupyterhub/jupyterhub
version: 1.1.12
version: 1.1.13
bitnami/jupyterhub/README.md
+4 -4
View File
@@ -87,7 +87,7 @@ The command removes all the Kubernetes components associated with the chart and
| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | ---------------------- |
| `hub.image.registry` | Hub image registry | `docker.io` |
| `hub.image.repository` | Hub image repository | `bitnami/jupyterhub` |
| `hub.image.tag` | Hub image tag (immutable tags are recommended) | `1.5.0-debian-10-r107` |
| `hub.image.tag` | Hub image tag (immutable tags are recommended) | `1.5.0-debian-10-r149` |
| `hub.image.pullPolicy` | Hub image pull policy | `IfNotPresent` |
| `hub.image.pullSecrets` | Hub image pull secrets | `[]` |
| `hub.baseUrl` | Hub base URL | `/` |
@@ -213,7 +213,7 @@ The command removes all the Kubernetes components associated with the chart and
| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | --------------------------------- |
| `proxy.image.registry` | Proxy image registry | `docker.io` |
| `proxy.image.repository` | Proxy image repository | `bitnami/configurable-http-proxy` |
| `proxy.image.tag` | Proxy image tag (immutable tags are recommended) | `4.5.1-debian-10-r8` |
| `proxy.image.tag` | Proxy image tag (immutable tags are recommended) | `4.5.1-debian-10-r58` |
| `proxy.image.pullPolicy` | Proxy image pull policy | `IfNotPresent` |
| `proxy.image.pullSecrets` | Proxy image pull secrets | `[]` |
| `proxy.image.debug` | Activate verbose output | `false` |
@@ -401,7 +401,7 @@ The command removes all the Kubernetes components associated with the chart and
| ----------------------------------------------- | --------------------------------------------------------------------------------------------------- | ------------------------------------ |
| `singleuser.image.registry` | Single User image registry | `docker.io` |
| `singleuser.image.repository` | Single User image repository | `bitnami/jupyter-base-notebook` |
| `singleuser.image.tag` | Single User image tag (immutabe tags are recommended) | `1.5.0-debian-10-r106` |
| `singleuser.image.tag` | Single User image tag (immutabe tags are recommended) | `1.5.0-debian-10-r154` |
| `singleuser.image.pullPolicy` | Single User image pull policy | `IfNotPresent` |
| `singleuser.image.pullSecrets` | Single User image pull secrets | `[]` |
| `singleuser.notebookDir` | Notebook directory (it will be the same as the PVC volume mount) | `/opt/bitnami/jupyterhub-singleuser` |
@@ -463,7 +463,7 @@ The command removes all the Kubernetes components associated with the chart and
| ---------------------------- | --------------------------------------------------- | ----------------------- |
| `auxiliaryImage.registry` | Auxiliary image registry | `docker.io` |
| `auxiliaryImage.repository` | Auxiliary image repository | `bitnami/bitnami-shell` |
| `auxiliaryImage.tag` | Auxiliary image tag (immutabe tags are recommended) | `10-debian-10-r353` |
| `auxiliaryImage.tag` | Auxiliary image tag (immutabe tags are recommended) | `10-debian-10-r403` |
| `auxiliaryImage.pullPolicy` | Auxiliary image pull policy | `IfNotPresent` |
| `auxiliaryImage.pullSecrets` | Auxiliary image pull secrets | `[]` |
bitnami/jupyterhub/values.yaml
+2 -2
View File
@@ -1067,8 +1067,8 @@ proxy:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
##
tls: false
## @param proxy.ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
bitnami/keycloak/Chart.yaml
+1 -1
View File
@@ -26,4 +26,4 @@ name: keycloak
sources:
- https://github.com/bitnami/bitnami-docker-keycloak
- https://github.com/keycloak/keycloak
version: 7.1.18
version: 7.1.19
bitnami/keycloak/README.md
+3 -3
View File
@@ -84,7 +84,7 @@ The command removes all the Kubernetes components associated with the chart and
| --------------------------------- | --------------------------------------------------------------------------------------------- | ---------------------- |
| `image.registry` | Keycloak image registry | `docker.io` |
| `image.repository` | Keycloak image repository | `bitnami/keycloak` |
| `image.tag` | Keycloak image tag (immutable tags are recommended) | `16.1.1-debian-10-r36` |
| `image.tag` | Keycloak image tag (immutable tags are recommended) | `16.1.1-debian-10-r85` |
| `image.pullPolicy` | Keycloak image pull policy | `IfNotPresent` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |
| `image.debug` | Specify if debug logs should be enabled | `false` |
@@ -226,7 +226,7 @@ The command removes all the Kubernetes components associated with the chart and
| --------------------------------------------- | --------------------------------------------------------- | ------- |
| `serviceAccount.create` | Enable the creation of a ServiceAccount for Keycloak pods | `true` |
| `serviceAccount.name` | Name of the created ServiceAccount | `""` |
| `serviceAccount.automountServiceAccountToken` | Auto-mount the service account token in the pod | `false` |
| `serviceAccount.automountServiceAccountToken` | Auto-mount the service account token in the pod | `true` |
| `serviceAccount.annotations` | Additional custom annotations for the ServiceAccount | `{}` |
| `rbac.create` | Whether to create and use RBAC resources or not | `false` |
| `rbac.rules` | Custom RBAC rules | `[]` |
@@ -272,7 +272,7 @@ The command removes all the Kubernetes components associated with the chart and
| `keycloakConfigCli.enabled` | Whether to enable keycloak-config-cli job | `false` |
| `keycloakConfigCli.image.registry` | keycloak-config-cli container image registry | `docker.io` |
| `keycloakConfigCli.image.repository` | keycloak-config-cli container image repository | `bitnami/keycloak-config-cli` |
| `keycloakConfigCli.image.tag` | keycloak-config-cli container image tag | `4.7.0-debian-10-r14` |
| `keycloakConfigCli.image.tag` | keycloak-config-cli container image tag | `4.9.0-debian-10-r14` |
| `keycloakConfigCli.image.pullPolicy` | keycloak-config-cli container image pull policy | `IfNotPresent` |
| `keycloakConfigCli.image.pullSecrets` | keycloak-config-cli container image pull secrets | `[]` |
| `keycloakConfigCli.annotations` | Annotations for keycloak-config-cli job | `{}` |
bitnami/keycloak/values.yaml
+2 -2
View File
@@ -584,8 +584,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
##
tls: false
## @param ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
bitnami/kong/Chart.yaml
+1 -1
View File
@@ -34,4 +34,4 @@ name: kong
sources:
- https://github.com/bitnami/bitnami-docker-kong
- https://konghq.com/
version: 6.1.20
version: 6.1.21
bitnami/kong/README.md
+3 -3
View File
@@ -83,7 +83,7 @@ To uninstall/delete the `my-release` deployment:
| ------------------- | ------------------------------------------------------------------------------- | --------------------- |
| `image.registry` | kong image registry | `docker.io` |
| `image.repository` | kong image repository | `bitnami/kong` |
| `image.tag` | kong image tag (immutable tags are recommended) | `2.7.1-debian-10-r27` |
| `image.tag` | kong image tag (immutable tags are recommended) | `2.8.1-debian-10-r28` |
| `image.pullPolicy` | kong image pull policy | `IfNotPresent` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |
| `image.debug` | Enable image debug mode | `false` |
@@ -217,7 +217,7 @@ To uninstall/delete the `my-release` deployment:
| `ingressController.enabled` | Enable/disable the Kong Ingress Controller | `true` |
| `ingressController.image.registry` | Kong Ingress Controller image registry | `docker.io` |
| `ingressController.image.repository` | Kong Ingress Controller image name | `bitnami/kong-ingress-controller` |
| `ingressController.image.tag` | Kong Ingress Controller image tag | `2.2.1-debian-10-r9` |
| `ingressController.image.tag` | Kong Ingress Controller image tag | `2.3.1-debian-10-r25` |
| `ingressController.image.pullPolicy` | Kong Ingress Controller image pull policy | `IfNotPresent` |
| `ingressController.image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |
| `ingressController.proxyReadyTimeout` | Maximum time (in seconds) to wait for the Kong container to be ready | `300` |
@@ -293,7 +293,7 @@ To uninstall/delete the `my-release` deployment:
| `postgresql.architecture` | PostgreSQL architecture (`standalone` or `replication`) | `standalone` |
| `postgresql.image.registry` | PostgreSQL image registry | `docker.io` |
| `postgresql.image.repository` | PostgreSQL image repository | `bitnami/postgresql` |
| `postgresql.image.tag` | PostgreSQL image tag (immutable tags are recommended) | `11.15.0-debian-10-r20` |
| `postgresql.image.tag` | PostgreSQL image tag (immutable tags are recommended) | `11.15.0-debian-10-r84` |
| `postgresql.external.host` | Database host | `""` |
| `postgresql.external.port` | Database port number | `5432` |
| `postgresql.external.user` | Non-root username for Kong | `kong` |
bitnami/kong/values.yaml
+2 -2
View File
@@ -471,8 +471,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
##
tls: false
## @param ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
bitnami/kubeapps/Chart.yaml
+1 -1
View File
@@ -30,4 +30,4 @@ maintainers:
name: kubeapps
sources:
- https://github.com/vmware-tanzu/kubeapps
version: 8.0.16
version: 8.0.17
bitnami/kubeapps/templates/_helpers.tpl
+2 -2
View File
@@ -338,8 +338,8 @@ kubeapps: ingress.tls
to be used by the Ingress Controller.
Please use any of these alternatives:
- Use the `ingress.extraTls` and `ingress.secrets` parameters to provide your custom TLS certificates.
- Relay on cert-manager to create it by adding its supported annotations in `ingress.annotations`
- Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
- Rely on cert-manager to create it by adding its supported annotations in `ingress.annotations`
- Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
{{- end -}}
{{- end -}}
bitnami/kubeapps/values.yaml
+2 -2
View File
@@ -94,8 +94,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
##
tls: false
bitnami/logstash/Chart.yaml
+1 -1
View File
@@ -23,4 +23,4 @@ name: logstash
sources:
- https://github.com/bitnami/bitnami-docker-logstash
- https://www.elastic.co/products/logstash
version: 4.0.5
version: 4.0.6
bitnami/logstash/README.md
+8 -8
View File
@@ -7,7 +7,7 @@ Logstash is an open source data processing engine. It ingests data from multiple
[Overview of Logstash](http://logstash.net)
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
@@ -82,7 +82,7 @@ The command removes all the Kubernetes components associated with the chart and
| --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | --------------------------- |
| `image.registry` | Logstash image registry | `docker.io` |
| `image.repository` | Logstash image repository | `bitnami/logstash` |
| `image.tag` | Logstash image tag (immutable tags are recommended) | `8.1.2-debian-10-r0` |
| `image.tag` | Logstash image tag (immutable tags are recommended) | `8.2.0-debian-10-r0` |
| `image.pullPolicy` | Logstash image pull policy | `IfNotPresent` |
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |
| `image.debug` | Specify if debug logs should be enabled | `false` |
@@ -173,7 +173,7 @@ The command removes all the Kubernetes components associated with the chart and
| `volumePermissions.securityContext.runAsUser` | User ID for the volumePermissions init container | `0` |
| `volumePermissions.image.registry` | Init container volume-permissions image registry | `docker.io` |
| `volumePermissions.image.repository` | Init container volume-permissions image repository | `bitnami/bitnami-shell` |
| `volumePermissions.image.tag` | Init container volume-permissions image tag (immutable tags are recommended) | `10-debian-10-r387` |
| `volumePermissions.image.tag` | Init container volume-permissions image tag (immutable tags are recommended) | `10-debian-10-r414` |
| `volumePermissions.image.pullPolicy` | Init container volume-permissions image pull policy | `IfNotPresent` |
| `volumePermissions.image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |
| `volumePermissions.resources.limits` | Init container volume-permissions resource limits | `{}` |
@@ -193,10 +193,10 @@ The command removes all the Kubernetes components associated with the chart and
| `ingress.secrets` | If you're providing your own certificates, please use this to add the certificates as secrets | `[]` |
| `ingress.ingressClassName` | IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+) | `""` |
| `metrics.enabled` | Enable the export of Prometheus metrics | `false` |
| `metrics.image.registry` | Logstash Relay image registry | `docker.io` |
| `metrics.image.repository` | Logstash Relay image repository | `bitnami/logstash-exporter` |
| `metrics.image.tag` | Logstash Relay image tag (immutable tags are recommended) | `7.3.0-debian-10-r489` |
| `metrics.image.pullPolicy` | Logstash Relay image pull policy | `IfNotPresent` |
| `metrics.image.registry` | Logstash exporter image registry | `docker.io` |
| `metrics.image.repository` | Logstash exporter image repository | `bitnami/logstash-exporter` |
| `metrics.image.tag` | Logstash exporter image tag (immutable tags are recommended) | `7.3.0-debian-10-r517` |
| `metrics.image.pullPolicy` | Logstash exporter image pull policy | `IfNotPresent` |
| `metrics.image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |
| `metrics.resources.limits` | The resources limits for the Logstash Prometheus Exporter container | `{}` |
| `metrics.resources.requests` | The requested resources for the Logstash Prometheus Exporter container | `{}` |
@@ -370,4 +370,4 @@ Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
limitations under the License.
bitnami/logstash/values.yaml
+4 -4
View File
@@ -634,10 +634,10 @@ metrics:
enabled: false
## Bitnami Logstash Promtheus Exporter image
## ref: https://hub.docker.com/r/bitnami/logstash-exporter/tags/
## @param metrics.image.registry Logstash Relay image registry
## @param metrics.image.repository Logstash Relay image repository
## @param metrics.image.tag Logstash Relay image tag (immutable tags are recommended)
## @param metrics.image.pullPolicy Logstash Relay image pull policy
## @param metrics.image.registry Logstash exporter image registry
## @param metrics.image.repository Logstash exporter image repository
## @param metrics.image.tag Logstash exporter image tag (immutable tags are recommended)
## @param metrics.image.pullPolicy Logstash exporter image pull policy
## @param metrics.image.pullSecrets Specify docker-registry secret names as an array
##
image:
bitnami/nats/Chart.yaml
+1 -1
View File
@@ -24,4 +24,4 @@ name: nats
sources:
- https://github.com/bitnami/bitnami-docker-nats
- https://nats.io/
version: 7.1.19
version: 7.1.20
bitnami/nats/README.md
+2 -2
View File
@@ -80,7 +80,7 @@ The command removes all the Kubernetes components associated with the chart and
| ------------------------ | ----------------------------------------------------------------------------------------------------- | -------------------- |
| `image.registry` | NATS image registry | `docker.io` |
| `image.repository` | NATS image repository | `bitnami/nats` |
| `image.tag` | NATS image tag (immutable tags are recommended) | `2.7.0-debian-10-r0` |
| `image.tag` | NATS image tag (immutable tags are recommended) | `2.8.2-debian-10-r0` |
| `image.pullPolicy` | NATS image pull policy | `IfNotPresent` |
| `image.pullSecrets` | NATS image pull secrets | `[]` |
| `image.debug` | Enable NATS image debug mode | `false` |
@@ -215,7 +215,7 @@ The command removes all the Kubernetes components associated with the chart and
| `metrics.enabled` | Enable Prometheus metrics via exporter side-car | `false` |
| `metrics.image.registry` | Prometheus metrics exporter image registry | `docker.io` |
| `metrics.image.repository` | Prometheus metrics exporter image repository | `bitnami/nats-exporter` |
| `metrics.image.tag` | Prometheus metrics exporter image tag (immutable tags are recommended) | `0.9.0-debian-10-r70` |
| `metrics.image.tag` | Prometheus metrics exporter image tag (immutable tags are recommended) | `0.9.2-debian-10-r28` |
| `metrics.image.pullPolicy` | Prometheus metrics image pull policy | `IfNotPresent` |
| `metrics.image.pullSecrets` | Prometheus metrics image pull secrets | `[]` |
| `metrics.resources` | Metrics exporter resource requests and limits | `{}` |
bitnami/nats/values.yaml
+2 -2
View File
@@ -563,8 +563,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
##
tls: false
## @param ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
bitnami/oauth2-proxy/Chart.yaml
+1 -1
View File
@@ -30,4 +30,4 @@ name: oauth2-proxy
sources:
- https://github.com/bitnami/bitnami-docker-oauth2-proxy
- https://github.com/oauth2-proxy/oauth2-proxy
version: 2.0.20
version: 2.0.21
bitnami/oauth2-proxy/values.yaml
+2 -2
View File
@@ -157,8 +157,8 @@ ingress:
## @param ingress.tls Enable TLS configuration for the host defined at `ingress.hostname` parameter
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.tls=true` and `ingress.certManager=false`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.tls=true` and `ingress.certManager=false`
##
tls: false
## @param ingress.extraHosts An array with additional hostname(s) to be covered with the ingress record
bitnami/odoo/values.yaml
+2 -2
View File
@@ -464,8 +464,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.tls=true` and `ingress.certManager=false`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.tls=true` and `ingress.certManager=false`
##
tls: false
## @param ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
bitnami/osclass/Chart.yaml
+1 -1
View File
@@ -31,4 +31,4 @@ name: osclass
sources:
- https://github.com/bitnami/bitnami-docker-osclass
- https://osclass.org/
version: 14.0.1
version: 14.0.2
bitnami/osclass/values.yaml
+2 -2
View File
@@ -508,8 +508,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.tls=true` and `ingress.certManager=false`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.tls=true` and `ingress.certManager=false`
##
tls: false
## @param ingress.extraHosts An array with additional hostname(s) to be covered with the ingress record
bitnami/rabbitmq/Chart.yaml
+1 -1
View File
@@ -23,4 +23,4 @@ name: rabbitmq
sources:
- https://github.com/bitnami/bitnami-docker-rabbitmq
- https://www.rabbitmq.com
version: 9.0.6
version: 9.0.7
bitnami/rabbitmq/templates/_helpers.tpl
+2 -2
View File
@@ -200,8 +200,8 @@ rabbitmq: ingress.tls
to be used by the Ingress Controller.
Please use any of these alternatives:
- Use the `ingress.extraTls` and `ingress.secrets` parameters to provide your custom TLS certificates.
- Relay on cert-manager to create it by setting the corresponding annotations
- Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
- Rely on cert-manager to create it by setting the corresponding annotations
- Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
{{- end -}}
{{- end -}}
bitnami/rabbitmq/values.yaml
+2 -2
View File
@@ -908,8 +908,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: {{- printf "%s-tls" .Values.ingress.hostname }}
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
##
tls: false
## @param ingress.selfSigned Set this to true in order to create a TLS secret for this ingress record
bitnami/redmine/values.yaml
+2 -2
View File
@@ -456,8 +456,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.tls=true` and `ingress.certManager=false`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.tls=true` and `ingress.certManager=false`
##
tls: false
## @param ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
bitnami/solr/Chart.yaml
+1 -1
View File
@@ -27,4 +27,4 @@ name: solr
sources:
- https://github.com/bitnami/bitnami-docker-solr
- https://lucene.apache.org/solr/
version: 4.0.9
version: 4.0.10
bitnami/solr/values.yaml
+2 -2
View File
@@ -430,8 +430,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
##
tls: false
## @param ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
bitnami/sonarqube/Chart.yaml
+1 -1
View File
@@ -28,4 +28,4 @@ name: sonarqube
sources:
- https://github.com/bitnami/bitnami-docker-sonarqube
- https://github.com/SonarSource/sonarqube
version: 1.0.13
version: 1.0.14
bitnami/sonarqube/values.yaml
+2 -2
View File
@@ -444,8 +444,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
##
tls: false
## @param ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
bitnami/suitecrm/values.yaml
+2 -2
View File
@@ -607,8 +607,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting `ingress.certManager=true`
## - Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting `ingress.certManager=true`
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
##
tls: false
## @param ingress.extraHosts An array with additional hostname(s) to be covered with the ingress record
bitnami/thanos/Chart.yaml
+1 -1
View File
@@ -28,4 +28,4 @@ name: thanos
sources:
- https://github.com/bitnami/bitnami-docker-thanos
- https://thanos.io
version: 10.3.7
version: 10.3.8
bitnami/thanos/values.yaml
+19 -19
View File
@@ -560,8 +560,8 @@ query:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.query.ingress.hostname }}`
## You can:
## - Use the `query.ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `query.ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `query.ingress.selfSigned=true`
##
tls: false
## @param query.ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
@@ -643,8 +643,8 @@ query:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.query.ingress.grpc.hostname }}`
## You can:
## - Use the `query.ingress.grpc.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `query.ingress.grpc.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `query.ingress.grpc.selfSigned=true`
##
tls: false
## @param query.ingress.grpc.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
@@ -1051,8 +1051,8 @@ queryFrontend:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.queryFrontend.ingress.hostname }}`
## You can:
## - Use the `queryFrontend.ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `queryFrontend.ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `queryFrontend.ingress.selfSigned=true`
##
tls: false
## @param queryFrontend.ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
@@ -1433,8 +1433,8 @@ bucketweb:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.bucketweb.ingress.hostname }}`
## You can:
## - Use the `bucketweb.ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `bucketweb.ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `bucketweb.ingress.selfSigned=true`
##
tls: false
## @param bucketweb.ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
@@ -1795,8 +1795,8 @@ compactor:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.compactor.ingress.hostname }}`
## You can:
## - Use the `compactor.ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `compactor.ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `compactor.ingress.selfSigned=true`
##
tls: false
## @param compactor.ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
@@ -2179,7 +2179,7 @@ storegateway:
existingClaim: ""
## @param storegateway.automountServiceAccountToken Enable/disable auto mounting of the service account token only for the sts
##
automountServiceAccountToken: true
automountServiceAccountToken: true
## ServiceAccount configuration
## @param storegateway.serviceAccount.annotations Annotations for Thanos Store Gateway Service Account
## @param storegateway.serviceAccount.existingServiceAccount Name for an existing Thanos Store Gateway Service Account
@@ -2275,8 +2275,8 @@ storegateway:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.storegateway.ingress.hostname }}`
## You can:
## - Use the `storegateway.ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `storegateway.ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `storegateway.ingress.selfSigned=true`
##
tls: false
## @param storegateway.ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
@@ -2358,8 +2358,8 @@ storegateway:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.storegateway.ingress.grpc.hostname }}`
## You can:
## - Use the `storegateway.ingress.grpc.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `storegateway.ingress.grpc.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `storegateway.ingress.grpc.selfSigned=true`
##
tls: false
## @param storegateway.ingress.grpc.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
@@ -2755,7 +2755,7 @@ ruler:
existingClaim: ""
## @param ruler.automountServiceAccountToken Enable/disable auto mounting of the service account token only for the sts
##
automountServiceAccountToken: true
automountServiceAccountToken: true
## ServiceAccount configuration
## @param ruler.serviceAccount.annotations Annotations for Thanos Ruler Service Account
## @param ruler.serviceAccount.existingServiceAccount Name for an existing Thanos Ruler Service Account
@@ -3316,8 +3316,8 @@ receive:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.receive.ingress.hostname }}`
## You can:
## - Use the `receive.ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `receive.ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `receive.ingress.selfSigned=true`
##
tls: false
## @param receive.ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
@@ -3560,7 +3560,7 @@ receiveDistributor:
topologySpreadConstraints: []
## @param receiveDistributor.automountServiceAccountToken Enable/disable auto mounting of the service account token only for the deployment
##
automountServiceAccountToken: true
automountServiceAccountToken: true
## ServiceAccount configuration
## @param receiveDistributor.serviceAccount.annotations Annotations for Thanos Receive Distributor Service Account
## @param receiveDistributor.serviceAccount.existingServiceAccount Name for an existing Thanos Receive Distributor Service Account
bitnami/wildfly/Chart.yaml
+1 -1
View File
@@ -26,4 +26,4 @@ name: wildfly
sources:
- https://github.com/bitnami/bitnami-docker-wildfly
- http://wildfly.org
version: 13.2.7
version: 13.2.8
bitnami/wildfly/values.yaml
+2 -2
View File
@@ -431,8 +431,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.tls=true` and `ingress.certManager=false`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.tls=true` and `ingress.certManager=false`
##
tls: false
## @param ingress.extraHosts [array] An array with additional hostname(s) to be covered with the ingress record
bitnami/wordpress-intel/Chart.yaml
+1 -1
View File
@@ -35,4 +35,4 @@ name: wordpress-intel
sources:
- https://github.com/bitnami/bitnami-docker-wordpress-intel
- https://wordpress.org/
version: 1.0.6
version: 1.0.7
bitnami/wordpress-intel/values.yaml
+2 -2
View File
@@ -520,8 +520,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.tls=true` and `ingress.certManager=false`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.tls=true` and `ingress.certManager=false`
##
tls: false
## @param ingress.extraHosts An array with additional hostname(s) to be covered with the ingress record
bitnami/wordpress/Chart.yaml
+1 -1
View File
@@ -35,4 +35,4 @@ name: wordpress
sources:
- https://github.com/bitnami/bitnami-docker-wordpress
- https://wordpress.org/
version: 14.0.7
version: 14.0.8
bitnami/wordpress/values.yaml
+2 -2
View File
@@ -609,8 +609,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
##
tls: false
## @param ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
template/CHART_NAME/values.yaml
+2 -2
View File
@@ -449,8 +449,8 @@ ingress:
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
## You can:
## - Use the `ingress.secrets` parameter to create this TLS secret
## - Relay on cert-manager to create it by setting the corresponding annotations
## - Relay on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
## - Rely on cert-manager to create it by setting the corresponding annotations
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
##
tls: false
## @param ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm