[bitnami/rabbitmq-cluster-operator] Adapt CRDS for 1.10.0 version (#7813)

* [bitnami/rabbitmq-cluster-operator] Adapt CRDS for 1.10.0 version

Signed-off-by: juan131 <juanariza@vmware.com>

* [bitnami/rabbitmq-cluster-operator] Update components versions

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

Co-authored-by: Bitnami Containers <containers@bitnami.com>
This commit is contained in:
Juan Ariza Toledano
2021-10-14 18:28:33 +02:00
committed by GitHub
parent be89a00ab6
commit 117e129a1b
5 changed files with 232 additions and 798 deletions

View File

@@ -25,4 +25,4 @@ name: rabbitmq-cluster-operator
sources:
- https://github.com/bitnami/bitnami-docker-rabbitmq-cluster-operator
- https://github.com/rabbitmq/cluster-operator
version: 0.1.7
version: 1.0.0

View File

@@ -184,7 +184,6 @@ This solution allows to easily deploy multiple RabbitMQ instances compared to th
| `customStartupProbe` | Custom startupProbe that overrides the default one | `{}` |
| `resources.limits` | The resources limits for the RabbitMQ Cluster Operator containers | `{}` |
| `resources.requests` | The requested resources for the RabbitMQ Cluster Operator containers | `{}` |
| `installCRDs` | Install RabbitMQ Cluster CRD | `true` |
| `podSecurityContext.enabled` | Enabled RabbitMQ Cluster Operator pods' Security Context | `true` |
| `podSecurityContext.fsGroup` | Set RabbitMQ Cluster Operator pod's Security Context fsGroup | `1001` |
| `containerSecurityContext.enabled` | Enabled RabbitMQ Cluster Operator containers' Security Context | `true` |
@@ -318,3 +317,16 @@ extraDeploy:
## 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).
## Upgrading
### To 1.0.0
The CRD was updated according to the latest changes in the upstream project. Thanks to the improvements in the latest changes, the CRD is not templated anymore abd can be placed under the `crds` directory following [Helm best practices for CRDS](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/).
You need to manually delete the old CRD before upgrading the release.
```console
kubectl delete crd rabbitmqclusters.rabbitmq.com
helm upgrade my-release bitnami/rabbitmq-cluster-operator
```

View File

@@ -83,6 +83,8 @@ spec:
valueFrom:
fieldRef:
fieldPath: metadata.namespace
- name: DEFAULT_RABBITMQ_IMAGE
value: {{ template "rmqco.rabbitmq.image" . }}
{{- if .Values.extraEnvVars }}
{{- include "common.tplvalues.render" (dict "value" .Values.extraEnvVars "context" $) | nindent 12 }}
{{- end }}

View File

@@ -56,7 +56,7 @@ extraDeploy: []
image:
registry: docker.io
repository: bitnami/rabbitmq-cluster-operator
tag: 1.10.0-scratch-r0
tag: 1.10.0-scratch-r1
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: http://kubernetes.io/docs/user-guide/images/#pre-pulling-images
@@ -158,10 +158,6 @@ resources:
limits: {}
requests: {}
## @param installCRDs Install RabbitMQ Cluster CRD
##
installCRDs: true
## Configure Pods Security Context
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod
## @param podSecurityContext.enabled Enabled RabbitMQ Cluster Operator pods' Security Context