mirror of
https://github.com/bitnami/charts.git
synced 2026-03-08 00:37:41 +08:00
[bitnami/rabbitmq] fix: Remove postStart hook (#8855)
* [bitnami/rabbitmq] fix: Remove postStart hook Signed-off-by: Javier Salmeron Garcia <jsalmeron@vmware.com> * [bitnami/rabbitmq] Update components versions Signed-off-by: Bitnami Containers <containers@bitnami.com> Co-authored-by: Bitnami Containers <containers@bitnami.com>
This commit is contained in:
Javier J. Salmerón-García
committed by
GitHub
GitHub
parent
c0c986f8d5
commit
adc6b3d0fc
@@ -1,6 +1,6 @@
|
||||
dependencies:
|
||||
- name: common
|
||||
repository: https://charts.bitnami.com/bitnami
|
||||
version: 1.10.3
|
||||
digest: sha256:710e8247ae70ea63a2fb2fde4320511ff28c7b5c7a738861427f104a7718bdf4
|
||||
generated: "2021-12-02T17:29:16.053850737Z"
|
||||
version: 1.10.4
|
||||
digest: sha256:e177cdcd71e67a1e64e95260c4b780374e1d66e85be405d5dc58459654e49ffa
|
||||
generated: "2022-02-01T15:29:23.039004591Z"
|
||||
|
||||
@@ -8,7 +8,7 @@ dependencies:
|
||||
tags:
|
||||
- bitnami-common
|
||||
version: 1.x.x
|
||||
description: Open source message broker software that implements the Advanced Message Queuing Protocol (AMQP)
|
||||
description: RabbitMQ is an open source general-purpose message broker that is designed for consistent, highly-available messaging scenarios (both synchronous and asynchronous).
|
||||
engine: gotpl
|
||||
home: https://github.com/bitnami/charts/tree/master/bitnami/rabbitmq
|
||||
icon: https://bitnami.com/assets/stacks/rabbitmq/img/rabbitmq-stack-220x234.png
|
||||
@@ -23,4 +23,4 @@ name: rabbitmq
|
||||
sources:
|
||||
- https://github.com/bitnami/bitnami-docker-rabbitmq
|
||||
- https://www.rabbitmq.com
|
||||
version: 8.27.0
|
||||
version: 8.28.0
|
||||
|
||||
@@ -1,9 +1,13 @@
|
||||
<!--- app-name: RabbitMQ -->
|
||||
<!--- app-name: ®abbitMQ -->
|
||||
|
||||
# RabbitMQ
|
||||
# ®abbitMQ packaged by Bitnami
|
||||
|
||||
[RabbitMQ](https://www.rabbitmq.com/) is an open source multi-protocol message broker.
|
||||
®abbitMQ is an open source general-purpose message broker that is designed for consistent, highly-available messaging scenarios (both synchronous and asynchronous).
|
||||
|
||||
[Overview of ®abbitMQ](https://www.rabbitmq.com)
|
||||
|
||||
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
|
||||
|
||||
## TL;DR
|
||||
|
||||
```bash
|
||||
@@ -13,7 +17,7 @@ $ helm install my-release bitnami/rabbitmq
|
||||
|
||||
## Introduction
|
||||
|
||||
This chart bootstraps a [RabbitMQ](https://github.com/bitnami/bitnami-docker-rabbitmq) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
|
||||
This chart bootstraps a [®abbitMQ](https://github.com/bitnami/bitnami-docker-rabbitmq) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.
|
||||
|
||||
Bitnami charts can be used with [Kubeapps](https://kubeapps.com/) for deployment and management of Helm Charts in clusters. This chart has been tested to work with NGINX Ingress, cert-manager, fluentd and Prometheus on top of the [BKPR](https://kubeprod.io/).
|
||||
|
||||
@@ -31,7 +35,7 @@ To install the chart with the release name `my-release`:
|
||||
$ helm install my-release bitnami/rabbitmq
|
||||
```
|
||||
|
||||
The command deploys RabbitMQ on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
|
||||
The command deploys ®abbitMQ on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.
|
||||
|
||||
> **Tip**: List all releases using `helm list`
|
||||
|
||||
@@ -56,14 +60,14 @@ The command removes all the Kubernetes components associated with the chart and
|
||||
| `global.storageClass` | Global StorageClass for Persistent Volume(s) | `""` |
|
||||
|
||||
|
||||
### RabbitMQ Image parameters
|
||||
### ®abbitMQ Image parameters
|
||||
|
||||
| Name | Description | Value |
|
||||
| ------------------- | -------------------------------------------------------------- | --------------------- |
|
||||
| `image.registry` | RabbitMQ image registry | `docker.io` |
|
||||
| `image.repository` | RabbitMQ image repository | `bitnami/rabbitmq` |
|
||||
| `image.tag` | RabbitMQ image tag (immutable tags are recommended) | `3.9.13-debian-10-r2` |
|
||||
| `image.pullPolicy` | RabbitMQ image pull policy | `IfNotPresent` |
|
||||
| `image.registry` | ®abbitMQ image registry | `docker.io` |
|
||||
| `image.repository` | ®abbitMQ image repository | `bitnami/rabbitmq` |
|
||||
| `image.tag` | ®abbitMQ image tag (immutable tags are recommended) | `3.9.13-debian-10-r2` |
|
||||
| `image.pullPolicy` | ®abbitMQ image pull policy | `IfNotPresent` |
|
||||
| `image.pullSecrets` | Specify docker-registry secret names as an array | `[]` |
|
||||
| `image.debug` | Set to true if you would like to see extra information on logs | `false` |
|
||||
|
||||
@@ -82,46 +86,46 @@ The command removes all the Kubernetes components associated with the chart and
|
||||
| `diagnosticMode.args` | Args to override all containers in the deployment | `["infinity"]` |
|
||||
| `hostAliases` | Deployment pod host aliases | `[]` |
|
||||
| `commonAnnotations` | Annotations to add to all deployed objects | `{}` |
|
||||
| `auth.username` | RabbitMQ application username | `user` |
|
||||
| `auth.password` | RabbitMQ application password | `""` |
|
||||
| `auth.existingPasswordSecret` | Existing secret with RabbitMQ credentials (must contain a value for `rabbitmq-password` key) | `""` |
|
||||
| `auth.username` | ®abbitMQ application username | `user` |
|
||||
| `auth.password` | ®abbitMQ application password | `""` |
|
||||
| `auth.existingPasswordSecret` | Existing secret with ®abbitMQ credentials (must contain a value for `rabbitmq-password` key) | `""` |
|
||||
| `auth.erlangCookie` | Erlang cookie to determine whether different nodes are allowed to communicate with each other | `""` |
|
||||
| `auth.existingErlangSecret` | Existing secret with RabbitMQ Erlang cookie (must contain a value for `rabbitmq-erlang-cookie` key) | `""` |
|
||||
| `auth.tls.enabled` | Enable TLS support on RabbitMQ | `false` |
|
||||
| `auth.existingErlangSecret` | Existing secret with ®abbitMQ Erlang cookie (must contain a value for `rabbitmq-erlang-cookie` key) | `""` |
|
||||
| `auth.tls.enabled` | Enable TLS support on ®abbitMQ | `false` |
|
||||
| `auth.tls.autoGenerated` | Generate automatically self-signed TLS certificates | `false` |
|
||||
| `auth.tls.failIfNoPeerCert` | When set to true, TLS connection will be rejected if client fails to provide a certificate | `true` |
|
||||
| `auth.tls.sslOptionsVerify` | Should [peer verification](https://www.rabbitmq.com/ssl.html#peer-verification) be enabled? | `verify_peer` |
|
||||
| `auth.tls.caCertificate` | Certificate Authority (CA) bundle content | `""` |
|
||||
| `auth.tls.serverCertificate` | Server certificate content | `""` |
|
||||
| `auth.tls.serverKey` | Server private key content | `""` |
|
||||
| `auth.tls.existingSecret` | Existing secret with certificate content to RabbitMQ credentials | `""` |
|
||||
| `auth.tls.existingSecret` | Existing secret with certificate content to ®abbitMQ credentials | `""` |
|
||||
| `auth.tls.existingSecretFullChain` | Whether or not the existing secret contains the full chain in the certificate (`tls.crt`). Will be used in place of `ca.cert` if `true`. | `false` |
|
||||
| `logs` | Path of the RabbitMQ server's Erlang log file. Value for the `RABBITMQ_LOGS` environment variable | `-` |
|
||||
| `ulimitNofiles` | RabbitMQ Max File Descriptors | `65536` |
|
||||
| `maxAvailableSchedulers` | RabbitMQ maximum available scheduler threads | `""` |
|
||||
| `onlineSchedulers` | RabbitMQ online scheduler threads | `""` |
|
||||
| `memoryHighWatermark.enabled` | Enable configuring Memory high watermark on RabbitMQ | `false` |
|
||||
| `logs` | Path of the ®abbitMQ server's Erlang log file. Value for the `RABBITMQ_LOGS` environment variable | `-` |
|
||||
| `ulimitNofiles` | ®abbitMQ Max File Descriptors | `65536` |
|
||||
| `maxAvailableSchedulers` | ®abbitMQ maximum available scheduler threads | `""` |
|
||||
| `onlineSchedulers` | ®abbitMQ online scheduler threads | `""` |
|
||||
| `memoryHighWatermark.enabled` | Enable configuring Memory high watermark on ®abbitMQ | `false` |
|
||||
| `memoryHighWatermark.type` | Memory high watermark type. Either `absolute` or `relative` | `relative` |
|
||||
| `memoryHighWatermark.value` | Memory high watermark value | `0.4` |
|
||||
| `plugins` | List of default plugins to enable (should only be altered to remove defaults; for additional plugins use `extraPlugins`) | `rabbitmq_management rabbitmq_peer_discovery_k8s` |
|
||||
| `communityPlugins` | List of Community plugins (URLs) to be downloaded during container initialization | `""` |
|
||||
| `extraPlugins` | Extra plugins to enable (single string containing a space-separated list) | `rabbitmq_auth_backend_ldap` |
|
||||
| `clustering.enabled` | Enable RabbitMQ clustering | `true` |
|
||||
| `clustering.enabled` | Enable ®abbitMQ clustering | `true` |
|
||||
| `clustering.addressType` | Switch clustering mode. Either `ip` or `hostname` | `hostname` |
|
||||
| `clustering.rebalance` | Rebalance master for queues in cluster when new replica is created | `false` |
|
||||
| `clustering.forceBoot` | Force boot of an unexpectedly shut down cluster (in an unexpected order). | `false` |
|
||||
| `clustering.partitionHandling` | Switch Partition Handling Strategy. Either `autoheal` or `pause-minority` or `pause-if-all-down` or `ignore` | `autoheal` |
|
||||
| `loadDefinition.enabled` | Enable loading a RabbitMQ definitions file to configure RabbitMQ | `false` |
|
||||
| `loadDefinition.enabled` | Enable loading a ®abbitMQ definitions file to configure ®abbitMQ | `false` |
|
||||
| `loadDefinition.existingSecret` | Existing secret with the load definitions file | `""` |
|
||||
| `command` | Override default container command (useful when using custom images) | `[]` |
|
||||
| `args` | Override default container args (useful when using custom images) | `[]` |
|
||||
| `terminationGracePeriodSeconds` | Default duration in seconds k8s waits for container to exit before sending kill signal. | `120` |
|
||||
| `extraEnvVars` | Extra environment variables to add to RabbitMQ pods | `[]` |
|
||||
| `extraEnvVars` | Extra environment variables to add to ®abbitMQ pods | `[]` |
|
||||
| `extraEnvVarsCM` | Name of existing ConfigMap containing extra environment variables | `""` |
|
||||
| `extraEnvVarsSecret` | Name of existing Secret containing extra environment variables (in case of sensitive data) | `""` |
|
||||
| `extraContainerPorts` | Extra ports to be included in container spec, primarily informational | `[]` |
|
||||
| `configuration` | RabbitMQ Configuration file content: required cluster configuration | `""` |
|
||||
| `extraConfiguration` | Configuration file content: extra configuration to be appended to RabbitMQ configuration | `""` |
|
||||
| `configuration` | ®abbitMQ Configuration file content: required cluster configuration | `""` |
|
||||
| `extraConfiguration` | Configuration file content: extra configuration to be appended to ®abbitMQ configuration | `""` |
|
||||
| `advancedConfiguration` | Configuration file content: advanced configuration | `""` |
|
||||
| `ldap.enabled` | Enable LDAP support | `false` |
|
||||
| `ldap.servers` | List of LDAP servers hostnames | `[]` |
|
||||
@@ -138,14 +142,14 @@ The command removes all the Kubernetes components associated with the chart and
|
||||
|
||||
| Name | Description | Value |
|
||||
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ | --------------- |
|
||||
| `replicaCount` | Number of RabbitMQ replicas to deploy | `1` |
|
||||
| `replicaCount` | Number of ®abbitMQ replicas to deploy | `1` |
|
||||
| `schedulerName` | Use an alternate scheduler, e.g. "stork". | `""` |
|
||||
| `podManagementPolicy` | Pod management policy | `OrderedReady` |
|
||||
| `podLabels` | RabbitMQ Pod labels. Evaluated as a template | `{}` |
|
||||
| `podAnnotations` | RabbitMQ Pod annotations. Evaluated as a template | `{}` |
|
||||
| `updateStrategyType` | Update strategy type for RabbitMQ statefulset | `RollingUpdate` |
|
||||
| `statefulsetLabels` | RabbitMQ statefulset labels. Evaluated as a template | `{}` |
|
||||
| `priorityClassName` | Name of the priority class to be used by RabbitMQ pods, priority class needs to be created beforehand | `""` |
|
||||
| `podLabels` | ®abbitMQ Pod labels. Evaluated as a template | `{}` |
|
||||
| `podAnnotations` | ®abbitMQ Pod annotations. Evaluated as a template | `{}` |
|
||||
| `updateStrategyType` | Update strategy type for ®abbitMQ statefulset | `RollingUpdate` |
|
||||
| `statefulsetLabels` | ®abbitMQ statefulset labels. Evaluated as a template | `{}` |
|
||||
| `priorityClassName` | Name of the priority class to be used by ®abbitMQ pods, priority class needs to be created beforehand | `""` |
|
||||
| `podAffinityPreset` | Pod affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `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` | `""` |
|
||||
@@ -155,12 +159,12 @@ The command removes all the Kubernetes components associated with the chart and
|
||||
| `nodeSelector` | Node labels for pod assignment. Evaluated as a template | `{}` |
|
||||
| `tolerations` | Tolerations for pod assignment. Evaluated as a template | `[]` |
|
||||
| `topologySpreadConstraints` | Topology Spread Constraints for pod assignment spread across your cluster among failure-domains. Evaluated as a template | `[]` |
|
||||
| `podSecurityContext.enabled` | Enable RabbitMQ pods' Security Context | `true` |
|
||||
| `podSecurityContext.enabled` | Enable ®abbitMQ pods' Security Context | `true` |
|
||||
| `podSecurityContext.fsGroup` | Group ID for the filesystem used by the containers | `1001` |
|
||||
| `podSecurityContext.runAsUser` | User ID for the service user running the pod | `1001` |
|
||||
| `containerSecurityContext` | RabbitMQ containers' Security Context | `{}` |
|
||||
| `resources.limits` | The resources limits for RabbitMQ containers | `{}` |
|
||||
| `resources.requests` | The requested resources for RabbitMQ containers | `{}` |
|
||||
| `containerSecurityContext` | ®abbitMQ containers' Security Context | `{}` |
|
||||
| `resources.limits` | The resources limits for ®abbitMQ containers | `{}` |
|
||||
| `resources.requests` | The requested resources for ®abbitMQ containers | `{}` |
|
||||
| `livenessProbe.enabled` | Enable livenessProbe | `true` |
|
||||
| `livenessProbe.initialDelaySeconds` | Initial delay seconds for livenessProbe | `120` |
|
||||
| `livenessProbe.periodSeconds` | Period seconds for livenessProbe | `30` |
|
||||
@@ -176,8 +180,8 @@ The command removes all the Kubernetes components associated with the chart and
|
||||
| `customLivenessProbe` | Override default liveness probe | `{}` |
|
||||
| `customReadinessProbe` | Override default readiness probe | `{}` |
|
||||
| `customStartupProbe` | Define a custom startup probe | `{}` |
|
||||
| `initContainers` | Add init containers to the RabbitMQ pod | `[]` |
|
||||
| `sidecars` | Add sidecar containers to the RabbitMQ pod | `[]` |
|
||||
| `initContainers` | Add init containers to the ®abbitMQ pod | `[]` |
|
||||
| `sidecars` | Add sidecar containers to the ®abbitMQ pod | `[]` |
|
||||
| `pdb.create` | Enable/disable a Pod Disruption Budget creation | `false` |
|
||||
| `pdb.minAvailable` | Minimum number/percentage of pods that should remain scheduled | `1` |
|
||||
| `pdb.maxUnavailable` | Maximum number/percentage of pods that may be made unavailable | `""` |
|
||||
@@ -187,7 +191,7 @@ The command removes all the Kubernetes components associated with the chart and
|
||||
|
||||
| Name | Description | Value |
|
||||
| --------------------------------------------- | --------------------------------------------------- | ------ |
|
||||
| `serviceAccount.create` | Enable creation of ServiceAccount for RabbitMQ pods | `true` |
|
||||
| `serviceAccount.create` | Enable creation of ServiceAccount for ®abbitMQ pods | `true` |
|
||||
| `serviceAccount.name` | Name of the created serviceAccount | `""` |
|
||||
| `serviceAccount.automountServiceAccountToken` | Auto-mount the service account token in the pod | `true` |
|
||||
| `rbac.create` | Whether RBAC rules should be created | `true` |
|
||||
@@ -197,12 +201,12 @@ The command removes all the Kubernetes components associated with the chart and
|
||||
|
||||
| Name | Description | Value |
|
||||
| --------------------------- | ------------------------------------------------ | --------------- |
|
||||
| `persistence.enabled` | Enable RabbitMQ data persistence using PVC | `true` |
|
||||
| `persistence.storageClass` | PVC Storage Class for RabbitMQ data volume | `""` |
|
||||
| `persistence.enabled` | Enable ®abbitMQ data persistence using PVC | `true` |
|
||||
| `persistence.storageClass` | PVC Storage Class for ®abbitMQ data volume | `""` |
|
||||
| `persistence.selector` | Selector to match an existing Persistent Volume | `{}` |
|
||||
| `persistence.accessMode` | PVC Access Mode for RabbitMQ data volume | `ReadWriteOnce` |
|
||||
| `persistence.accessMode` | PVC Access Mode for ®abbitMQ data volume | `ReadWriteOnce` |
|
||||
| `persistence.existingClaim` | Provide an existing PersistentVolumeClaims | `""` |
|
||||
| `persistence.size` | PVC Storage Request for RabbitMQ data volume | `8Gi` |
|
||||
| `persistence.size` | PVC Storage Request for ®abbitMQ data volume | `8Gi` |
|
||||
| `persistence.volumes` | Additional volumes without creating PVC | `[]` |
|
||||
| `persistence.annotations` | Persistence annotations. Evaluated as a template | `{}` |
|
||||
|
||||
@@ -223,14 +227,14 @@ The command removes all the Kubernetes components associated with the chart and
|
||||
| `service.distPort` | Erlang distribution server port | `25672` |
|
||||
| `service.distPortName` | Erlang distribution service port name | `dist` |
|
||||
| `service.distNodePort` | Node port override for `dist` port, if serviceType is `NodePort` | `""` |
|
||||
| `service.managerPortEnabled` | RabbitMQ Manager port | `true` |
|
||||
| `service.managerPort` | RabbitMQ Manager port | `15672` |
|
||||
| `service.managerPortName` | RabbitMQ Manager service port name | `http-stats` |
|
||||
| `service.managerPortEnabled` | ®abbitMQ Manager port | `true` |
|
||||
| `service.managerPort` | ®abbitMQ Manager port | `15672` |
|
||||
| `service.managerPortName` | ®abbitMQ Manager service port name | `http-stats` |
|
||||
| `service.managerNodePort` | Node port override for `http-stats` port, if serviceType `NodePort` | `""` |
|
||||
| `service.metricsPort` | RabbitMQ Prometheues metrics port | `9419` |
|
||||
| `service.metricsPortName` | RabbitMQ Prometheues metrics service port name | `metrics` |
|
||||
| `service.metricsPort` | ®abbitMQ Prometheues metrics port | `9419` |
|
||||
| `service.metricsPortName` | ®abbitMQ Prometheues metrics service port name | `metrics` |
|
||||
| `service.metricsNodePort` | Node port override for `metrics` port, if serviceType is `NodePort` | `""` |
|
||||
| `service.epmdPortEnabled` | RabbitMQ EPMD Discovery service port | `true` |
|
||||
| `service.epmdPortEnabled` | ®abbitMQ EPMD Discovery service port | `true` |
|
||||
| `service.epmdNodePort` | Node port override for `epmd` port, if serviceType is `NodePort` | `""` |
|
||||
| `service.epmdPortName` | EPMD Discovery service port name | `epmd` |
|
||||
| `service.extraPorts` | Extra ports to expose in the service | `[]` |
|
||||
@@ -261,8 +265,8 @@ The command removes all the Kubernetes components associated with the chart and
|
||||
|
||||
| Name | Description | Value |
|
||||
| ------------------------------------------ | ------------------------------------------------------------------------------------------------------ | --------------------- |
|
||||
| `metrics.enabled` | Enable exposing RabbitMQ metrics to be gathered by Prometheus | `false` |
|
||||
| `metrics.plugins` | Plugins to enable Prometheus metrics in RabbitMQ | `rabbitmq_prometheus` |
|
||||
| `metrics.enabled` | Enable exposing ®abbitMQ metrics to be gathered by Prometheus | `false` |
|
||||
| `metrics.plugins` | Plugins to enable Prometheus metrics in ®abbitMQ | `rabbitmq_prometheus` |
|
||||
| `metrics.podAnnotations` | Annotations for enabling prometheus to access the metrics endpoint | `{}` |
|
||||
| `metrics.serviceMonitor.enabled` | Create ServiceMonitor Resource for scraping metrics using PrometheusOperator | `false` |
|
||||
| `metrics.serviceMonitor.namespace` | Specify the namespace in which the serviceMonitor resource will be created | `""` |
|
||||
@@ -306,7 +310,7 @@ $ helm install my-release \
|
||||
bitnami/rabbitmq
|
||||
```
|
||||
|
||||
The above command sets the RabbitMQ admin username and password to `admin` and `secretpassword` respectively. Additionally the secure erlang cookie is set to `secretcookie`.
|
||||
The above command sets the ®abbitMQ admin username and password to `admin` and `secretpassword` respectively. Additionally the secure erlang cookie is set to `secretcookie`.
|
||||
|
||||
> NOTE: Once this chart is deployed, it is not possible to change the application's access credentials, such as usernames or passwords, using Helm. To change these application credentials after deployment, delete any persistent volumes (PVs) used by the chart and re-deploy it, or use the application's built-in administrative tools if available.
|
||||
|
||||
@@ -341,13 +345,13 @@ To horizontally scale this chart once it has been deployed, two options are avai
|
||||
|
||||
> NOTE: It is mandatory to specify the password and Erlang cookie that was set the first time the chart was installed when upgrading the chart.
|
||||
|
||||
When scaling down the solution, unnecessary RabbitMQ nodes are automatically stopped, but they are not removed from the cluster. You need to manually remove them by running the `rabbitmqctl forget_cluster_node` command.
|
||||
When scaling down the solution, unnecessary ®abbitMQ nodes are automatically stopped, but they are not removed from the cluster. You need to manually remove them by running the `rabbitmqctl forget_cluster_node` command.
|
||||
|
||||
Refer to the chart documentation for [more information on scaling the Rabbit cluster horizontally](https://docs.bitnami.com/kubernetes/infrastructure/rabbitmq/administration/scale-deployment/).
|
||||
|
||||
### Enable TLS support
|
||||
|
||||
To enable TLS support, first generate the certificates as described in the [RabbitMQ documentation for SSL certificate generation](https://www.rabbitmq.com/ssl.html#automated-certificate-generation).
|
||||
To enable TLS support, first generate the certificates as described in the [®abbitMQ documentation for SSL certificate generation](https://www.rabbitmq.com/ssl.html#automated-certificate-generation).
|
||||
|
||||
Once the certificates are generated, you have two alternatives:
|
||||
|
||||
@@ -362,9 +366,9 @@ Refer to the chart documentation for [more information and examples of enabling
|
||||
|
||||
### Load custom definitions
|
||||
|
||||
It is possible to [load a RabbitMQ definitions file to configure RabbitMQ](https://www.rabbitmq.com/management.html#load-definitions).
|
||||
It is possible to [load a ®abbitMQ definitions file to configure ®abbitMQ](https://www.rabbitmq.com/management.html#load-definitions).
|
||||
|
||||
Because definitions may contain RabbitMQ credentials, [store the JSON as a Kubernetes secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-secrets-as-files-from-a-pod). Within the secret's data, choose a key name that corresponds with the desired load definitions filename (i.e. `load_definition.json`) and use the JSON object as the value.
|
||||
Because definitions may contain ®abbitMQ credentials, [store the JSON as a Kubernetes secret](https://kubernetes.io/docs/concepts/configuration/secret/#using-secrets-as-files-from-a-pod). Within the secret's data, choose a key name that corresponds with the desired load definitions filename (i.e. `load_definition.json`) and use the JSON object as the value.
|
||||
|
||||
Next, specify the `load_definitions` property as an `extraConfiguration` pointing to the load definition file path within the container (i.e. `/app/load_definition.json`) and set `loadDefinition.enable` to `true`. Any load definitions specified will be available within in the container at `/app`.
|
||||
|
||||
@@ -380,9 +384,9 @@ LDAP support can be enabled in the chart by specifying the `ldap.*` parameters w
|
||||
|
||||
### Configure memory high watermark
|
||||
|
||||
It is possible to configure a memory high watermark on RabbitMQ to define [memory thresholds](https://www.rabbitmq.com/memory.html#threshold) using the `memoryHighWatermark.*` parameters. To do so, you have two alternatives:
|
||||
It is possible to configure a memory high watermark on ®abbitMQ to define [memory thresholds](https://www.rabbitmq.com/memory.html#threshold) using the `memoryHighWatermark.*` parameters. To do so, you have two alternatives:
|
||||
|
||||
* Set an absolute limit of RAM to be used on each RabbitMQ node, as shown in the configuration example below:
|
||||
* Set an absolute limit of RAM to be used on each ®abbitMQ node, as shown in the configuration example below:
|
||||
|
||||
```
|
||||
memoryHighWatermark.enabled="true"
|
||||
@@ -390,7 +394,7 @@ memoryHighWatermark.type="absolute"
|
||||
memoryHighWatermark.value="512MB"
|
||||
```
|
||||
|
||||
* Set a relative limit of RAM to be used on each RabbitMQ node. To enable this feature, define the memory limits at pod level too. An example configuration is shown below:
|
||||
* Set a relative limit of RAM to be used on each ®abbitMQ node. To enable this feature, define the memory limits at pod level too. An example configuration is shown below:
|
||||
|
||||
```
|
||||
memoryHighWatermark.enabled="true"
|
||||
@@ -413,17 +417,17 @@ Alternatively, you can use a ConfigMap or a Secret with the environment variable
|
||||
|
||||
### Use plugins
|
||||
|
||||
The Bitnami Docker RabbitMQ image ships a set of plugins by default. By default, this chart enables `rabbitmq_management` and `rabbitmq_peer_discovery_k8s` since they are required for RabbitMQ to work on K8s.
|
||||
The Bitnami Docker ®abbitMQ image ships a set of plugins by default. By default, this chart enables `rabbitmq_management` and `rabbitmq_peer_discovery_k8s` since they are required for ®abbitMQ to work on K8s.
|
||||
|
||||
To enable extra plugins, set the `extraPlugins` parameter with the list of plugins you want to enable. In addition to this, the `communityPlugins` parameter can be used to specify a list of URLs (separated by spaces) for custom plugins for RabbitMQ.
|
||||
To enable extra plugins, set the `extraPlugins` parameter with the list of plugins you want to enable. In addition to this, the `communityPlugins` parameter can be used to specify a list of URLs (separated by spaces) for custom plugins for ®abbitMQ.
|
||||
|
||||
Refer to the chart documentation for [more information on using RabbitMQ plugins](https://docs.bitnami.com/kubernetes/infrastructure/rabbitmq/configuration/use-plugins/).
|
||||
Refer to the chart documentation for [more information on using ®abbitMQ plugins](https://docs.bitnami.com/kubernetes/infrastructure/rabbitmq/configuration/use-plugins/).
|
||||
|
||||
### Recover the cluster from complete shutdown
|
||||
|
||||
> IMPORTANT: Some of these procedures can lead to data loss. Always make a backup beforehand.
|
||||
|
||||
The RabbitMQ cluster is able to support multiple node failures but, in a situation in which all the nodes are brought down at the same time, the cluster might not be able to self-recover.
|
||||
The ®abbitMQ cluster is able to support multiple node failures but, in a situation in which all the nodes are brought down at the same time, the cluster might not be able to self-recover.
|
||||
|
||||
This happens if the pod management policy of the statefulset is not `Parallel` and the last pod to be running wasn't the first pod of the statefulset. If that happens, update the pod management policy to recover a healthy state:
|
||||
|
||||
@@ -438,7 +442,7 @@ $ helm upgrade RELEASE_NAME bitnami/rabbitmq \
|
||||
|
||||
For a faster resyncronization of the nodes, you can temporarily disable the readiness probe by setting `readinessProbe.enabled=false`. Bear in mind that the pods will be exposed before they are actually ready to process requests.
|
||||
|
||||
If the steps above don't bring the cluster to a healthy state, it could be possible that none of the RabbitMQ nodes think they were the last node to be up during the shutdown. In those cases, you can force the boot of the nodes by specifying the `clustering.forceBoot=true` parameter (which will execute [`rabbitmqctl force_boot`](https://www.rabbitmq.com/rabbitmqctl.8.html#force_boot) in each pod):
|
||||
If the steps above don't bring the cluster to a healthy state, it could be possible that none of the ®abbitMQ nodes think they were the last node to be up during the shutdown. In those cases, you can force the boot of the nodes by specifying the `clustering.forceBoot=true` parameter (which will execute [`rabbitmqctl force_boot`](https://www.rabbitmq.com/rabbitmqctl.8.html#force_boot) in each pod):
|
||||
|
||||
```console
|
||||
$ helm upgrade RELEASE_NAME bitnami/rabbitmq \
|
||||
@@ -453,11 +457,11 @@ More information: [Clustering Guide: Restarting](https://www.rabbitmq.com/cluste
|
||||
|
||||
### Known issues
|
||||
|
||||
- Changing the password through RabbitMQ's UI can make the pod fail due to the default liveness probes. If you do so, remember to make the chart aware of the new password. Updating the default secret with the password you set through RabbitMQ's UI will automatically recreate the pods. If you are using your own secret, you may have to manually recreate the pods.
|
||||
- Changing the password through ®abbitMQ's UI can make the pod fail due to the default liveness probes. If you do so, remember to make the chart aware of the new password. Updating the default secret with the password you set through ®abbitMQ's UI will automatically recreate the pods. If you are using your own secret, you may have to manually recreate the pods.
|
||||
|
||||
## 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.
|
||||
The [Bitnami ®abbitMQ](https://github.com/bitnami/bitnami-docker-rabbitmq) image stores the ®abbitMQ data and configurations at the `/opt/bitnami/rabbitmq/var/lib/rabbitmq/` path of the container.
|
||||
|
||||
The chart mounts a [Persistent Volume](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) at this location. By default, the volume is created using dynamic volume provisioning. An existing PersistentVolumeClaim can also be defined.
|
||||
|
||||
@@ -496,7 +500,7 @@ extraConfiguration: |-
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
Find more information about how to deal with common errors related to Bitnami’s Helm charts in [this troubleshooting guide](https://docs.bitnami.com/general/how-to/troubleshoot-helm-chart-issues).
|
||||
Find more information about how to deal with common errors related to Bitnami<EFBFBD><EFBFBD><EFBFBD>s Helm charts in [this troubleshooting guide](https://docs.bitnami.com/general/how-to/troubleshoot-helm-chart-issues).
|
||||
|
||||
## Upgrading
|
||||
|
||||
@@ -510,9 +514,9 @@ $ helm upgrade my-release bitnami/rabbitmq --set auth.password=[PASSWORD] --set
|
||||
|
||||
### To 8.21.0
|
||||
|
||||
This new version of the chart bumps the RabbitMQ version to `3.9.1`. It is considered a minor release, and no breaking changes are expected. Additionally, RabbitMQ `3.9.X` nodes can run alongside `3.8.X` nodes.
|
||||
This new version of the chart bumps the ®abbitMQ version to `3.9.1`. It is considered a minor release, and no breaking changes are expected. Additionally, ®abbitMQ `3.9.X` nodes can run alongside `3.8.X` nodes.
|
||||
|
||||
See the [Upgrading guide](https://www.rabbitmq.com/upgrade.html) and the [RabbitMQ change log](https://www.rabbitmq.com/changelog.html) for further documentation.
|
||||
See the [Upgrading guide](https://www.rabbitmq.com/upgrade.html) and the [®abbitMQ change log](https://www.rabbitmq.com/changelog.html) for further documentation.
|
||||
|
||||
### To 8.0.0
|
||||
|
||||
@@ -551,7 +555,7 @@ Consequences:
|
||||
|
||||
### To 6.0.0
|
||||
|
||||
This new version updates the RabbitMQ image to a [new version based on bash instead of node.js](https://github.com/bitnami/bitnami-docker-rabbitmq#3715-r18-3715-ol-7-r19). However, since this Chart overwrites the container's command, the changes to the container shouldn't affect the Chart. To upgrade, it may be needed to enable the `fastBoot` option, as it is already the case from upgrading from 5.X to 5.Y.
|
||||
This new version updates the ®abbitMQ image to a [new version based on bash instead of node.js](https://github.com/bitnami/bitnami-docker-rabbitmq#3715-r18-3715-ol-7-r19). However, since this Chart overwrites the container's command, the changes to the container shouldn't affect the Chart. To upgrade, it may be needed to enable the `fastBoot` option, as it is already the case from upgrading from 5.X to 5.Y.
|
||||
|
||||
### To 5.0.0
|
||||
|
||||
@@ -573,7 +577,7 @@ $ kubectl delete statefulset rabbitmq --cascade=false
|
||||
|
||||
Bitnami Kubernetes documentation is available at [https://docs.bitnami.com/](https://docs.bitnami.com/). You can find there the following resources:
|
||||
|
||||
- [Documentation for RabbitMQ Helm chart](https://docs.bitnami.com/kubernetes/infrastructure/rabbitmq/)
|
||||
- [Documentation for ®abbitMQ Helm chart](https://docs.bitnami.com/kubernetes/infrastructure/rabbitmq/)
|
||||
- [Get Started with Kubernetes guides](https://docs.bitnami.com/kubernetes/)
|
||||
- [Bitnami Helm charts documentation](https://docs.bitnami.com/kubernetes/apps/)
|
||||
- [Kubernetes FAQs](https://docs.bitnami.com/kubernetes/faq/)
|
||||
@@ -593,4 +597,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.
|
||||
@@ -173,6 +173,10 @@ spec:
|
||||
secretKeyRef:
|
||||
name: {{ template "rabbitmq.secretErlangName" . }}
|
||||
key: rabbitmq-erlang-cookie
|
||||
{{- if and .Values.clustering.rebalance (gt (.Values.replicaCount | int) 1) }}
|
||||
- name: RABBITMQ_CLUSTER_REBALANCE
|
||||
value: "true"
|
||||
{{- end }}
|
||||
{{- if .Values.loadDefinition.enabled }}
|
||||
- name: RABBITMQ_LOAD_DEFINITIONS
|
||||
value: "yes"
|
||||
@@ -268,19 +272,6 @@ spec:
|
||||
startupProbe: {{- include "common.tplvalues.render" (dict "value" .Values.customStartupProbe "context" $) | nindent 12 }}
|
||||
{{- end }}
|
||||
lifecycle:
|
||||
{{- if and .Values.clustering.rebalance (gt (.Values.replicaCount | int) 1) }}
|
||||
postStart:
|
||||
exec:
|
||||
command:
|
||||
- /bin/bash
|
||||
- -ec
|
||||
- |
|
||||
until rabbitmqctl cluster_status >/dev/null; do
|
||||
echo "Waiting for cluster readiness..."
|
||||
sleep 5
|
||||
done
|
||||
rabbitmq-queues rebalance "all"
|
||||
{{- end }}
|
||||
preStop:
|
||||
exec:
|
||||
command:
|
||||
|
||||
@@ -16,20 +16,20 @@ global:
|
||||
imagePullSecrets: []
|
||||
storageClass: ""
|
||||
|
||||
## @section RabbitMQ Image parameters
|
||||
## Bitnami RabbitMQ image version
|
||||
## @section ®abbitMQ Image parameters
|
||||
## Bitnami ®abbitMQ image version
|
||||
## ref: https://hub.docker.com/r/bitnami/rabbitmq/tags/
|
||||
## @param image.registry RabbitMQ image registry
|
||||
## @param image.repository RabbitMQ image repository
|
||||
## @param image.tag RabbitMQ image tag (immutable tags are recommended)
|
||||
## @param image.pullPolicy RabbitMQ image pull policy
|
||||
## @param image.registry ®abbitMQ image registry
|
||||
## @param image.repository ®abbitMQ image repository
|
||||
## @param image.tag ®abbitMQ image tag (immutable tags are recommended)
|
||||
## @param image.pullPolicy ®abbitMQ image pull policy
|
||||
## @param image.pullSecrets Specify docker-registry secret names as an array
|
||||
## @param image.debug Set to true if you would like to see extra information on logs
|
||||
##
|
||||
image:
|
||||
registry: docker.io
|
||||
repository: bitnami/rabbitmq
|
||||
tag: 3.9.13-debian-10-r2
|
||||
tag: 3.9.13-debian-10-r13
|
||||
|
||||
## set to true if you would like to see extra information on logs
|
||||
## It turns BASH and/or NAMI debugging in the image
|
||||
@@ -94,19 +94,19 @@ hostAliases: []
|
||||
## @param commonAnnotations Annotations to add to all deployed objects
|
||||
##
|
||||
commonAnnotations: {}
|
||||
## RabbitMQ Authentication parameters
|
||||
## ®abbitMQ Authentication parameters
|
||||
##
|
||||
auth:
|
||||
## @param auth.username RabbitMQ application username
|
||||
## @param auth.username ®abbitMQ application username
|
||||
## ref: https://github.com/bitnami/bitnami-docker-rabbitmq#environment-variables
|
||||
##
|
||||
username: user
|
||||
|
||||
## @param auth.password RabbitMQ application password
|
||||
## @param auth.password ®abbitMQ application password
|
||||
## ref: https://github.com/bitnami/bitnami-docker-rabbitmq#environment-variables
|
||||
##
|
||||
password: ""
|
||||
## @param auth.existingPasswordSecret Existing secret with RabbitMQ credentials (must contain a value for `rabbitmq-password` key)
|
||||
## @param auth.existingPasswordSecret Existing secret with ®abbitMQ credentials (must contain a value for `rabbitmq-password` key)
|
||||
## e.g:
|
||||
## existingPasswordSecret: name-of-existing-secret
|
||||
##
|
||||
@@ -116,7 +116,7 @@ auth:
|
||||
## ref: https://github.com/bitnami/bitnami-docker-rabbitmq#environment-variables
|
||||
##
|
||||
erlangCookie: ""
|
||||
## @param auth.existingErlangSecret Existing secret with RabbitMQ Erlang cookie (must contain a value for `rabbitmq-erlang-cookie` key)
|
||||
## @param auth.existingErlangSecret Existing secret with ®abbitMQ Erlang cookie (must contain a value for `rabbitmq-erlang-cookie` key)
|
||||
## e.g:
|
||||
## existingErlangSecret: name-of-existing-secret
|
||||
##
|
||||
@@ -124,14 +124,14 @@ auth:
|
||||
|
||||
## Enable encryption to rabbitmq
|
||||
## ref: https://www.rabbitmq.com/ssl.html
|
||||
## @param auth.tls.enabled Enable TLS support on RabbitMQ
|
||||
## @param auth.tls.enabled Enable TLS support on ®abbitMQ
|
||||
## @param auth.tls.autoGenerated Generate automatically self-signed TLS certificates
|
||||
## @param auth.tls.failIfNoPeerCert When set to true, TLS connection will be rejected if client fails to provide a certificate
|
||||
## @param auth.tls.sslOptionsVerify Should [peer verification](https://www.rabbitmq.com/ssl.html#peer-verification) be enabled?
|
||||
## @param auth.tls.caCertificate Certificate Authority (CA) bundle content
|
||||
## @param auth.tls.serverCertificate Server certificate content
|
||||
## @param auth.tls.serverKey Server private key content
|
||||
## @param auth.tls.existingSecret Existing secret with certificate content to RabbitMQ credentials
|
||||
## @param auth.tls.existingSecret Existing secret with certificate content to ®abbitMQ credentials
|
||||
## @param auth.tls.existingSecretFullChain Whether or not the existing secret contains the full chain in the certificate (`tls.crt`). Will be used in place of `ca.cert` if `true`.
|
||||
##
|
||||
tls:
|
||||
@@ -145,32 +145,32 @@ auth:
|
||||
existingSecret: ""
|
||||
existingSecretFullChain: false
|
||||
|
||||
## @param logs Path of the RabbitMQ server's Erlang log file. Value for the `RABBITMQ_LOGS` environment variable
|
||||
## @param logs Path of the ®abbitMQ server's Erlang log file. Value for the `RABBITMQ_LOGS` environment variable
|
||||
## ref: https://www.rabbitmq.com/logging.html#log-file-location
|
||||
##
|
||||
logs: "-"
|
||||
|
||||
## @param ulimitNofiles RabbitMQ Max File Descriptors
|
||||
## @param ulimitNofiles ®abbitMQ Max File Descriptors
|
||||
## ref: https://github.com/bitnami/bitnami-docker-rabbitmq#environment-variables
|
||||
## ref: https://www.rabbitmq.com/install-debian.html#kernel-resource-limits
|
||||
##
|
||||
ulimitNofiles: "65536"
|
||||
|
||||
## RabbitMQ maximum available scheduler threads and online scheduler threads. By default it will create a thread per CPU detected, with the following parameters you can tune it manually.
|
||||
## ®abbitMQ maximum available scheduler threads and online scheduler threads. By default it will create a thread per CPU detected, with the following parameters you can tune it manually.
|
||||
## ref: https://hamidreza-s.github.io/erlang/scheduling/real-time/preemptive/migration/2016/02/09/erlang-scheduler-details.html#scheduler-threads
|
||||
## ref: https://github.com/bitnami/charts/issues/2189
|
||||
## @param maxAvailableSchedulers RabbitMQ maximum available scheduler threads
|
||||
## @param onlineSchedulers RabbitMQ online scheduler threads
|
||||
## @param maxAvailableSchedulers ®abbitMQ maximum available scheduler threads
|
||||
## @param onlineSchedulers ®abbitMQ online scheduler threads
|
||||
##
|
||||
maxAvailableSchedulers: ""
|
||||
onlineSchedulers: ""
|
||||
|
||||
## The memory threshold under which RabbitMQ will stop reading from client network sockets, in order to avoid being killed by the OS
|
||||
## The memory threshold under which ®abbitMQ will stop reading from client network sockets, in order to avoid being killed by the OS
|
||||
## ref: https://www.rabbitmq.com/alarms.html
|
||||
## ref: https://www.rabbitmq.com/memory.html#threshold
|
||||
##
|
||||
memoryHighWatermark:
|
||||
## @param memoryHighWatermark.enabled Enable configuring Memory high watermark on RabbitMQ
|
||||
## @param memoryHighWatermark.enabled Enable configuring Memory high watermark on ®abbitMQ
|
||||
##
|
||||
enabled: false
|
||||
## @param memoryHighWatermark.type Memory high watermark type. Either `absolute` or `relative`
|
||||
@@ -201,7 +201,7 @@ extraPlugins: "rabbitmq_auth_backend_ldap"
|
||||
## Clustering settings
|
||||
##
|
||||
clustering:
|
||||
## @param clustering.enabled Enable RabbitMQ clustering
|
||||
## @param clustering.enabled Enable ®abbitMQ clustering
|
||||
##
|
||||
enabled: true
|
||||
## @param clustering.addressType Switch clustering mode. Either `ip` or `hostname`
|
||||
@@ -223,10 +223,10 @@ clustering:
|
||||
##
|
||||
partitionHandling: autoheal
|
||||
|
||||
## Loading a RabbitMQ definitions file to configure RabbitMQ
|
||||
## Loading a ®abbitMQ definitions file to configure ®abbitMQ
|
||||
##
|
||||
loadDefinition:
|
||||
## @param loadDefinition.enabled Enable loading a RabbitMQ definitions file to configure RabbitMQ
|
||||
## @param loadDefinition.enabled Enable loading a ®abbitMQ definitions file to configure ®abbitMQ
|
||||
##
|
||||
enabled: false
|
||||
## @param loadDefinition.existingSecret Existing secret with the load definitions file
|
||||
@@ -246,7 +246,7 @@ args: []
|
||||
##
|
||||
terminationGracePeriodSeconds: 120
|
||||
|
||||
## @param extraEnvVars Extra environment variables to add to RabbitMQ pods
|
||||
## @param extraEnvVars Extra environment variables to add to ®abbitMQ pods
|
||||
## E.g:
|
||||
## extraEnvVars:
|
||||
## - name: FOO
|
||||
@@ -270,7 +270,7 @@ extraEnvVarsSecret: ""
|
||||
##
|
||||
extraContainerPorts: []
|
||||
|
||||
## @param configuration [string] RabbitMQ Configuration file content: required cluster configuration
|
||||
## @param configuration [string] ®abbitMQ Configuration file content: required cluster configuration
|
||||
## Do not override unless you know what you are doing.
|
||||
## To add more configuration, use `extraConfiguration` of `advancedConfiguration` instead
|
||||
##
|
||||
@@ -327,7 +327,7 @@ configuration: |-
|
||||
vm_memory_high_watermark.{{ .Values.memoryHighWatermark.type }} = {{ .Values.memoryHighWatermark.value }}
|
||||
{{- end }}
|
||||
|
||||
## @param extraConfiguration [string] Configuration file content: extra configuration to be appended to RabbitMQ configuration
|
||||
## @param extraConfiguration [string] Configuration file content: extra configuration to be appended to ®abbitMQ configuration
|
||||
## Use this instead of `configuration` to add more configuration
|
||||
##
|
||||
extraConfiguration: |-
|
||||
@@ -410,7 +410,7 @@ extraSecretsPrependReleaseName: false
|
||||
|
||||
## @section Statefulset parameters
|
||||
|
||||
## @param replicaCount Number of RabbitMQ replicas to deploy
|
||||
## @param replicaCount Number of ®abbitMQ replicas to deploy
|
||||
##
|
||||
replicaCount: 1
|
||||
|
||||
@@ -419,40 +419,40 @@ replicaCount: 1
|
||||
##
|
||||
schedulerName: ""
|
||||
|
||||
## RabbitMQ should be initialized one by one when building cluster for the first time.
|
||||
## ®abbitMQ should be initialized one by one when building cluster for the first time.
|
||||
## Therefore, the default value of podManagementPolicy is 'OrderedReady'
|
||||
## Once the RabbitMQ participates in the cluster, it waits for a response from another
|
||||
## RabbitMQ in the same cluster at reboot, except the last RabbitMQ of the same cluster.
|
||||
## Once the ®abbitMQ participates in the cluster, it waits for a response from another
|
||||
## ®abbitMQ in the same cluster at reboot, except the last ®abbitMQ of the same cluster.
|
||||
## If the cluster exits gracefully, you do not need to change the podManagementPolicy
|
||||
## because the first RabbitMQ of the statefulset always will be last of the cluster.
|
||||
## However if the last RabbitMQ of the cluster is not the first RabbitMQ due to a failure,
|
||||
## because the first ®abbitMQ of the statefulset always will be last of the cluster.
|
||||
## However if the last ®abbitMQ of the cluster is not the first ®abbitMQ due to a failure,
|
||||
## you must change podManagementPolicy to 'Parallel'.
|
||||
## ref : https://www.rabbitmq.com/clustering.html#restarting
|
||||
## @param podManagementPolicy Pod management policy
|
||||
##
|
||||
podManagementPolicy: OrderedReady
|
||||
|
||||
## @param podLabels RabbitMQ Pod labels. Evaluated as a template
|
||||
## @param podLabels ®abbitMQ Pod labels. Evaluated as a template
|
||||
## Ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
|
||||
##
|
||||
podLabels: {}
|
||||
|
||||
## @param podAnnotations RabbitMQ Pod annotations. Evaluated as a template
|
||||
## @param podAnnotations ®abbitMQ Pod annotations. Evaluated as a template
|
||||
## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/
|
||||
##
|
||||
podAnnotations: {}
|
||||
|
||||
## @param updateStrategyType Update strategy type for RabbitMQ statefulset
|
||||
## @param updateStrategyType Update strategy type for ®abbitMQ statefulset
|
||||
## ref: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#update-strategies
|
||||
##
|
||||
updateStrategyType: RollingUpdate
|
||||
|
||||
## @param statefulsetLabels RabbitMQ statefulset labels. Evaluated as a template
|
||||
## @param statefulsetLabels ®abbitMQ statefulset labels. Evaluated as a template
|
||||
## Ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
|
||||
##
|
||||
statefulsetLabels: {}
|
||||
|
||||
## @param priorityClassName Name of the priority class to be used by RabbitMQ pods, priority class needs to be created beforehand
|
||||
## @param priorityClassName Name of the priority class to be used by ®abbitMQ pods, priority class needs to be created beforehand
|
||||
## Ref: https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/
|
||||
##
|
||||
priorityClassName: ""
|
||||
@@ -508,9 +508,9 @@ tolerations: []
|
||||
##
|
||||
topologySpreadConstraints: []
|
||||
|
||||
## RabbitMQ pods' Security Context
|
||||
## ®abbitMQ pods' Security Context
|
||||
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod
|
||||
## @param podSecurityContext.enabled Enable RabbitMQ pods' Security Context
|
||||
## @param podSecurityContext.enabled Enable ®abbitMQ pods' Security Context
|
||||
## @param podSecurityContext.fsGroup Group ID for the filesystem used by the containers
|
||||
## @param podSecurityContext.runAsUser User ID for the service user running the pod
|
||||
##
|
||||
@@ -519,7 +519,7 @@ podSecurityContext:
|
||||
fsGroup: 1001
|
||||
runAsUser: 1001
|
||||
|
||||
## @param containerSecurityContext RabbitMQ containers' Security Context
|
||||
## @param containerSecurityContext ®abbitMQ containers' Security Context
|
||||
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-container
|
||||
## Example:
|
||||
## containerSecurityContext:
|
||||
@@ -529,14 +529,14 @@ podSecurityContext:
|
||||
##
|
||||
containerSecurityContext: {}
|
||||
|
||||
## RabbitMQ containers' resource requests and limits
|
||||
## ®abbitMQ containers' resource requests and limits
|
||||
## ref: https://kubernetes.io/docs/user-guide/compute-resources/
|
||||
## We usually recommend not to specify default resources and to leave this as a conscious
|
||||
## choice for the user. This also increases chances charts run on environments with little
|
||||
## resources, such as Minikube. If you do want to specify resources, uncomment the following
|
||||
## lines, adjust them as necessary, and remove the curly braces after 'resources:'.
|
||||
## @param resources.limits The resources limits for RabbitMQ containers
|
||||
## @param resources.requests The requested resources for RabbitMQ containers
|
||||
## @param resources.limits The resources limits for ®abbitMQ containers
|
||||
## @param resources.requests The requested resources for ®abbitMQ containers
|
||||
##
|
||||
resources:
|
||||
## Example:
|
||||
@@ -550,7 +550,7 @@ resources:
|
||||
## memory: 2Gi
|
||||
requests: {}
|
||||
|
||||
## Configure RabbitMQ containers' extra options for liveness probe
|
||||
## Configure ®abbitMQ containers' extra options for liveness probe
|
||||
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes
|
||||
## @param livenessProbe.enabled Enable livenessProbe
|
||||
## @param livenessProbe.initialDelaySeconds Initial delay seconds for livenessProbe
|
||||
@@ -566,7 +566,7 @@ livenessProbe:
|
||||
periodSeconds: 30
|
||||
failureThreshold: 6
|
||||
successThreshold: 1
|
||||
## Configure RabbitMQ containers' extra options for readiness probe
|
||||
## Configure ®abbitMQ containers' extra options for readiness probe
|
||||
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes
|
||||
## @param readinessProbe.enabled Enable readinessProbe
|
||||
## @param readinessProbe.initialDelaySeconds Initial delay seconds for readinessProbe
|
||||
@@ -596,7 +596,7 @@ customReadinessProbe: {}
|
||||
##
|
||||
customStartupProbe: {}
|
||||
|
||||
## @param initContainers Add init containers to the RabbitMQ pod
|
||||
## @param initContainers Add init containers to the ®abbitMQ pod
|
||||
## Example:
|
||||
## initContainers:
|
||||
## - name: your-image-name
|
||||
@@ -608,7 +608,7 @@ customStartupProbe: {}
|
||||
##
|
||||
initContainers: []
|
||||
|
||||
## @param sidecars Add sidecar containers to the RabbitMQ pod
|
||||
## @param sidecars Add sidecar containers to the ®abbitMQ pod
|
||||
## Example:
|
||||
## sidecars:
|
||||
## - name: your-image-name
|
||||
@@ -636,11 +636,11 @@ pdb:
|
||||
|
||||
## @section RBAC parameters
|
||||
|
||||
## RabbitMQ pods ServiceAccount
|
||||
## ®abbitMQ pods ServiceAccount
|
||||
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/
|
||||
##
|
||||
serviceAccount:
|
||||
## @param serviceAccount.create Enable creation of ServiceAccount for RabbitMQ pods
|
||||
## @param serviceAccount.create Enable creation of ServiceAccount for ®abbitMQ pods
|
||||
##
|
||||
create: true
|
||||
## @param serviceAccount.name Name of the created serviceAccount
|
||||
@@ -656,19 +656,19 @@ serviceAccount:
|
||||
##
|
||||
rbac:
|
||||
## @param rbac.create Whether RBAC rules should be created
|
||||
## binding RabbitMQ ServiceAccount to a role
|
||||
## that allows RabbitMQ pods querying the K8s API
|
||||
## binding ®abbitMQ ServiceAccount to a role
|
||||
## that allows ®abbitMQ pods querying the K8s API
|
||||
##
|
||||
create: true
|
||||
|
||||
## @section Persistence parameters
|
||||
|
||||
persistence:
|
||||
## @param persistence.enabled Enable RabbitMQ data persistence using PVC
|
||||
## @param persistence.enabled Enable ®abbitMQ data persistence using PVC
|
||||
##
|
||||
enabled: true
|
||||
|
||||
## @param persistence.storageClass PVC Storage Class for RabbitMQ data volume
|
||||
## @param persistence.storageClass PVC Storage Class for ®abbitMQ data volume
|
||||
## If defined, storageClassName: <storageClass>
|
||||
## If set to "-", storageClassName: "", which disables dynamic provisioning
|
||||
## If undefined (the default) or set to null, no storageClassName spec is
|
||||
@@ -682,7 +682,7 @@ persistence:
|
||||
## app: my-app
|
||||
##
|
||||
selector: {}
|
||||
## @param persistence.accessMode PVC Access Mode for RabbitMQ data volume
|
||||
## @param persistence.accessMode PVC Access Mode for ®abbitMQ data volume
|
||||
##
|
||||
accessMode: ReadWriteOnce
|
||||
|
||||
@@ -692,7 +692,7 @@ persistence:
|
||||
##
|
||||
existingClaim: ""
|
||||
|
||||
## @param persistence.size PVC Storage Request for RabbitMQ data volume
|
||||
## @param persistence.size PVC Storage Request for ®abbitMQ data volume
|
||||
## If you change this value, you might have to adjust `rabbitmq.diskFreeLimit` as well
|
||||
##
|
||||
size: 8Gi
|
||||
@@ -770,16 +770,16 @@ service:
|
||||
##
|
||||
distNodePort: ""
|
||||
|
||||
## @param service.managerPortEnabled RabbitMQ Manager port
|
||||
## @param service.managerPortEnabled ®abbitMQ Manager port
|
||||
## ref: https://github.com/bitnami/bitnami-docker-rabbitmq#environment-variables
|
||||
##
|
||||
managerPortEnabled: true
|
||||
|
||||
## @param service.managerPort RabbitMQ Manager port
|
||||
## @param service.managerPort ®abbitMQ Manager port
|
||||
##
|
||||
managerPort: 15672
|
||||
|
||||
## @param service.managerPortName RabbitMQ Manager service port name
|
||||
## @param service.managerPortName ®abbitMQ Manager service port name
|
||||
##
|
||||
managerPortName: http-stats
|
||||
|
||||
@@ -789,11 +789,11 @@ service:
|
||||
##
|
||||
managerNodePort: ""
|
||||
|
||||
## @param service.metricsPort RabbitMQ Prometheues metrics port
|
||||
## @param service.metricsPort ®abbitMQ Prometheues metrics port
|
||||
##
|
||||
metricsPort: 9419
|
||||
|
||||
## @param service.metricsPortName RabbitMQ Prometheues metrics service port name
|
||||
## @param service.metricsPortName ®abbitMQ Prometheues metrics service port name
|
||||
##
|
||||
metricsPortName: metrics
|
||||
|
||||
@@ -803,7 +803,7 @@ service:
|
||||
##
|
||||
metricsNodePort: ""
|
||||
|
||||
## @param service.epmdPortEnabled RabbitMQ EPMD Discovery service port
|
||||
## @param service.epmdPortEnabled ®abbitMQ EPMD Discovery service port
|
||||
##
|
||||
epmdPortEnabled: true
|
||||
|
||||
@@ -865,7 +865,7 @@ service:
|
||||
annotationsHeadless: {}
|
||||
|
||||
## Configure the ingress resource that allows you to access the
|
||||
## RabbitMQ installation. Set up the URL
|
||||
## ®abbitMQ installation. Set up the URL
|
||||
## ref: https://kubernetes.io/docs/user-guide/ingress/
|
||||
##
|
||||
ingress:
|
||||
@@ -971,8 +971,8 @@ networkPolicy:
|
||||
enabled: false
|
||||
## @param networkPolicy.allowExternal Don't require client label for connections
|
||||
## The Policy model to apply. When set to false, only pods with the correct
|
||||
## client label will have network access to the ports RabbitMQ is listening
|
||||
## on. When true, RabbitMQ will accept connections from any source
|
||||
## client label will have network access to the ports ®abbitMQ is listening
|
||||
## on. When true, ®abbitMQ will accept connections from any source
|
||||
## (with the correct destination port).
|
||||
##
|
||||
allowExternal: true
|
||||
@@ -994,11 +994,11 @@ networkPolicy:
|
||||
## Prometheus Metrics
|
||||
##
|
||||
metrics:
|
||||
## @param metrics.enabled Enable exposing RabbitMQ metrics to be gathered by Prometheus
|
||||
## @param metrics.enabled Enable exposing ®abbitMQ metrics to be gathered by Prometheus
|
||||
##
|
||||
enabled: false
|
||||
|
||||
## @param metrics.plugins Plugins to enable Prometheus metrics in RabbitMQ
|
||||
## @param metrics.plugins Plugins to enable Prometheus metrics in ®abbitMQ
|
||||
##
|
||||
plugins: "rabbitmq_prometheus"
|
||||
## Prometheus pod annotations
|
||||
@@ -1082,7 +1082,7 @@ metrics:
|
||||
## severity: error
|
||||
## annotations:
|
||||
## summary: Rabbitmq down (instance {{ "{{ $labels.instance }}" }})
|
||||
## description: RabbitMQ node down
|
||||
## description: ®abbitMQ node down
|
||||
## - alert: ClusterDown
|
||||
## expr: |
|
||||
## sum(rabbitmq_running{service="{{ template "rabbitmq.fullname" . }}"})
|
||||
@@ -1093,7 +1093,7 @@ metrics:
|
||||
## annotations:
|
||||
## summary: Cluster down (instance {{ "{{ $labels.instance }}" }})
|
||||
## description: |
|
||||
## Less than {{ .Values.replicaCount }} nodes running in RabbitMQ cluster
|
||||
## Less than {{ .Values.replicaCount }} nodes running in ®abbitMQ cluster
|
||||
## VALUE = {{ "{{ $value }}" }}
|
||||
## - alert: ClusterPartition
|
||||
## expr: rabbitmq_partitions{service="{{ template "rabbitmq.fullname" . }}"} > 0
|
||||
@@ -1126,7 +1126,7 @@ metrics:
|
||||
## annotations:
|
||||
## summary: Too many connections (instance {{ "{{ $labels.instance }}" }})
|
||||
## description: |
|
||||
## RabbitMQ instance has too many connections (> 1000)
|
||||
## ®abbitMQ instance has too many connections (> 1000)
|
||||
## VALUE = {{ "{{ $value }}" }}\n LABELS: {{ "{{ $labels }}" }}
|
||||
##
|
||||
rules: []
|
||||
@@ -1150,7 +1150,7 @@ volumePermissions:
|
||||
image:
|
||||
registry: docker.io
|
||||
repository: bitnami/bitnami-shell
|
||||
tag: 10-debian-10-r313
|
||||
tag: 10-debian-10-r326
|
||||
## Specify a imagePullPolicy
|
||||
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
|
||||
## ref: https://kubernetes.io/docs/user-guide/images/#pre-pulling-images
|
||||
|
||||
Reference in New Issue
Block a user