Synchronize upstreamed folder to 8b5d06ff4

upstreamed/joomla/Chart.yaml

@@ -1,7 +1,7 @@
 apiVersion: v1
 name: joomla
-version: 4.1.0
-appVersion: 3.9.3
+version: 4.1.1
+appVersion: 3.9.4
 description: PHP content management system (CMS) for publishing web content
 keywords:
 - joomla

upstreamed/joomla/values.yaml

@@ -13,7 +13,7 @@
 image:
   registry: docker.io
   repository: bitnami/joomla
-  tag: 3.9.3
+  tag: 3.9.4
   ## 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

upstreamed/rabbitmq/Chart.yaml

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

upstreamed/rabbitmq/README.md

@@ -130,6 +130,32 @@ $ helm install --name my-release -f values.yaml stable/rabbitmq
 
 > **Tip**: You can use the default [values.yaml](values.yaml)
 
+### Load Definitions
+It is possible to [load a RabbitMQ definitions file to configure RabbitMQ](http://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. For example:
+
+```yaml
+apiVersion: v1
+kind: Secret
+metadata:
+  name: rabbitmq-load-definition
+type: Opaque
+stringData:
+  load_definition.json: |-
+    {
+      "vhosts": [
+        {
+          "name": "/"
+        }
+      ]
+    }
+```
+
+Then, specify the `management.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`.
+
+> Loading a definition will take precedence over any configuration done through [Helm values](#configuration).
+
 ## Production configuration
 
 A standard configuration is provided by default that will run on most development environments. To operate this chart in a production environment, we recommend you use the alternative file values-production.yaml provided in this repository.

upstreamed/rabbitmq/templates/configuration.yaml

@@ -16,4 +16,3 @@ data:
     default_pass=CHANGEME
 {{ .Values.rabbitmq.configuration | indent 4 }}
 {{ .Values.rabbitmq.extraConfiguration | indent 4 }}
-

upstreamed/rabbitmq/templates/statefulset.yaml

@@ -82,6 +82,11 @@ spec:
             mountPath: /opt/bitnami/rabbitmq/conf
           - name: data
             mountPath: /opt/bitnami/rabbitmq/var/lib/rabbitmq/
+          {{- if .Values.rabbitmq.loadDefinition.enabled }}
+          - name: load-definition-volume
+            mountPath: /app
+            readOnly: true
+          {{- end }}
         ports:
         - name: epmd
           containerPort: 4369
@@ -204,6 +209,11 @@ spec:
               path: rabbitmq.conf
             - key: enabled_plugins
               path: enabled_plugins
+        {{- if .Values.rabbitmq.loadDefinition.enabled }}
+        - name: load-definition-volume
+          secret:
+            secretName: {{ .Values.rabbitmq.loadDefinition.secretName | quote }}
+        {{- end }}
       {{- if not .Values.persistence.enabled }}
         - name: data
           emptyDir: {}

upstreamed/rabbitmq/values-production.yaml

@@ -74,6 +74,10 @@ rabbitmq:
     address_type: ip
     k8s_domain: cluster.local
 
+  loadDefinition:
+    enabled: false
+    secretName: load-definition
+
   ## Configuration file content: required cluster configuration
   ## Do not override unless you know what you are doing. To add more configuration, use `extraConfiguration` instead
   configuration: |-
@@ -92,6 +96,7 @@ rabbitmq:
   ## Use this instead of `configuration` to add more configuration
   extraConfiguration: |-
     #disk_free_limit.absolute = 50MB
+    #management.load_definitions = /app/load_definition.json
 
 ## Kubernetes service type
 service:

upstreamed/rabbitmq/values.yaml

@@ -74,6 +74,10 @@ rabbitmq:
     address_type: ip
     k8s_domain: cluster.local
 
+  loadDefinition:
+    enabled: false
+    secretName: load-definition
+
   ## Configuration file content: required cluster configuration
   ## Do not override unless you know what you are doing. To add more configuration, use `extraConfiguration` instead
   configuration: |-
@@ -92,6 +96,7 @@ rabbitmq:
   ## Use this instead of  `configuration` to add more configuration
   extraConfiguration: |-
     #disk_free_limit.absolute = 50MB
+    #management.load_definitions = /app/load_definition.json
 
 ## Kubernetes service type
 service:

upstreamed/wordpress/Chart.yaml

@@ -1,7 +1,7 @@
 apiVersion: v1
 name: wordpress
-version: 5.6.0
-appVersion: 5.1.0
+version: 5.6.1
+appVersion: 5.1.1
 description: Web publishing platform for building blogs and websites.
 icon: https://bitnami.com/assets/stacks/wordpress/img/wordpress-stack-220x234.png
 keywords:

upstreamed/wordpress/values-production.yaml

@@ -13,7 +13,7 @@
 image:
   registry: docker.io
   repository: bitnami/wordpress
-  tag: 5.1.0
+  tag: 5.1.1
   pullPolicy: IfNotPresent
   ## Optionally specify an array of imagePullSecrets.
   ## Secrets must be manually created in the namespace.

upstreamed/wordpress/values.yaml

@@ -13,7 +13,7 @@
 image:
   registry: docker.io
   repository: bitnami/wordpress
-  tag: 5.1.0
+  tag: 5.1.1
   ## 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