Synchronize upstreamed folder to 989ee2980

This commit is contained in:
bitnami-bot
2019-10-02 15:35:00 +00:00
parent 1a1a5e54cd
commit 25a4151a78
8 changed files with 65 additions and 8 deletions

View File

@@ -1,6 +1,6 @@
apiVersion: v1
name: rabbitmq
version: 6.7.4
version: 6.8.0
appVersion: 3.7.18
description: Open source message broker software that implements the Advanced Message Queuing Protocol (AMQP)
keywords:

View File

@@ -152,6 +152,7 @@ The following table lists the configurable parameters of the RabbitMQ chart and
| `volumePermissions.image.pullPolicy` | Init container volume-permissions image pull policy | `Always` |
| `volumePermissions.resources` | Init container resource requests/limit | `nil` |
| `forceBoot.enabled` | Executes 'rabbitmqctl force_boot' to force boot cluster shut down unexpectedly in an unknown order. Use it only if you prefer availability over integrity. | `false` |
| `extraSecrets` | Optionally specify extra secrets to be created by the chart. | `{}` |
The above parameters map to the env variables defined in [bitnami/rabbitmq](http://github.com/bitnami/bitnami-docker-rabbitmq). For more information please refer to the [bitnami/rabbitmq](http://github.com/bitnami/bitnami-docker-rabbitmq) image documentation.
@@ -274,6 +275,27 @@ Any load definitions specified will be available within in the container at `/ap
> Loading a definition will take precedence over any configuration done through [Helm values](#configuration).
If needed, you can use `extraSecrets` to let the chart create the secret for you. This way, you don't need to manually create it before deploying a release. For example :
```yaml
extraSecrets:
load-definition:
load_definition.json: |
{
"vhosts": [
{
"name": "/"
}
]
}
rabbitmq:
loadDefinition:
enabled: true
secretName: load-definition
extraConfiguration: |
management.load_definitions = /app/load_definition.json
```
## Persistence
The [Bitnami RabbitMQ](https://github.com/bitnami/bitnami-docker-rabbitmq) image stores the RabbitMQ data and configurations at the `/opt/bitnami/rabbitmq/var/lib/rabbitmq/` path of the container.

View File

@@ -1,4 +1,4 @@
{{ if or (not .Values.rabbitmq.existingErlangSecret) (not .Values.rabbitmq.existingPasswordSecret) }}
{{- if or (not .Values.rabbitmq.existingErlangSecret) (not .Values.rabbitmq.existingPasswordSecret) }}
apiVersion: v1
kind: Secret
metadata:
@@ -20,4 +20,19 @@ data:
{{ else }}
rabbitmq-erlang-cookie: {{ randAlphaNum 32 | b64enc | quote }}
{{ end }}{{ end }}
{{ end }}
{{- end }}
{{- range $key, $value := .Values.extraSecrets }}
---
apiVersion: v1
kind: Secret
metadata:
name: {{ $key }}
labels:
app: {{ template "rabbitmq.name" $ }}
chart: {{ template "rabbitmq.chart" $ }}
release: "{{ $.Release.Name }}"
heritage: "{{ $.Release.Service }}"
type: Opaque
stringData:
{{ $value | toYaml | nindent 2 }}
{{- end }}

View File

@@ -388,3 +388,13 @@ volumePermissions:
##
forceBoot:
enabled: false
## Optionally specify extra secrets to be created by the chart.
## This can be useful when combined with load_definitions to automatically create the secret containing the definitions to be loaded.
##
extraSecrets: {}
# load_definition:
# load_definition.json: |
# {
# ...
# }

View File

@@ -388,3 +388,13 @@ volumePermissions:
##
forceBoot:
enabled: false
## Optionally specify extra secrets to be created by the chart.
## This can be useful when combined with load_definitions to automatically create the secret containing the definitions to be loaded.
##
extraSecrets: {}
# load_definition:
# load_definition.json: |
# {
# ...
# }