Charts CI

```
Updated:
  argo/argo-cd:
    - 5.51.4
  bitnami/airflow:
    - 16.1.5
  bitnami/cassandra:
    - 10.6.6
  bitnami/kafka:
    - 26.4.2
  bitnami/mariadb:
    - 14.1.4
  bitnami/mysql:
    - 9.14.4
  bitnami/postgresql:
    - 13.2.15
  bitnami/spark:
    - 8.1.6
  bitnami/tomcat:
    - 10.11.6
  bitnami/wordpress:
    - 18.1.15
  bitnami/zookeeper:
    - 12.3.3
  datadog/datadog:
    - 3.49.4
  haproxy/haproxy:
    - 1.35.1
  jenkins/jenkins:
    - 4.8.4
  jfrog/artifactory-ha:
    - 107.71.5
  jfrog/artifactory-jcr:
    - 107.71.5
  new-relic/nri-bundle:
    - 5.0.46
  speedscale/speedscale-operator:
    - 1.4.6
  stackstate/stackstate-k8s-agent:
    - 1.0.54
```

charts/argo/argo-cd/Chart.yaml

@@ -1,7 +1,7 @@
 annotations:
   artifacthub.io/changes: |
     - kind: changed
-      description: Replace non-existing examples with official example domain (RFC 2606)
+      description: Upgrade Argo CD to v2.9.2
   artifacthub.io/signKey: |
     fingerprint: 2B8F22F57260EFA67BE1C5824B11F800CD9D2252
     url: https://argoproj.github.io/argo-helm/pgp_keys.asc
@@ -11,7 +11,7 @@ annotations:
   catalog.cattle.io/kube-version: '>=1.23.0-0'
   catalog.cattle.io/release-name: argo-cd
 apiVersion: v2
-appVersion: v2.9.1
+appVersion: v2.9.2
 dependencies:
 - condition: redis-ha.enabled
   name: redis-ha
@@ -33,4 +33,4 @@ name: argo-cd
 sources:
 - https://github.com/argoproj/argo-helm/tree/main/charts/argo-cd
 - https://github.com/argoproj/argo-cd
-version: 5.51.3
+version: 5.51.4

charts/bitnami/airflow/Chart.lock

@@ -1,12 +1,12 @@
 dependencies:
 - name: redis
   repository: oci://registry-1.docker.io/bitnamicharts
-  version: 18.2.1
+  version: 18.4.0
 - name: postgresql
   repository: oci://registry-1.docker.io/bitnamicharts
-  version: 13.2.2
+  version: 13.2.15
 - name: common
   repository: oci://registry-1.docker.io/bitnamicharts
   version: 2.13.3
-digest: sha256:4adb05966b556cfdd809ce479d968d19030d6a967d066acdb997604c05afffd1
+digest: sha256:15580d67fba89ac0e98a4c479fa1ea4f9015b92d430745ce3f401841b34e3e3d
-generated: "2023-11-07T02:46:23.255235664Z"
+generated: "2023-11-22T00:02:07.834943162Z"

charts/bitnami/airflow/Chart.yaml

@@ -8,15 +8,15 @@ annotations:
     - name: airflow-exporter
       image: docker.io/bitnami/airflow-exporter:0.20220314.0-debian-11-r440
     - name: airflow-scheduler
-      image: docker.io/bitnami/airflow-scheduler:2.7.3-debian-11-r0
+      image: docker.io/bitnami/airflow-scheduler:2.7.3-debian-11-r1
     - name: airflow-worker
-      image: docker.io/bitnami/airflow-worker:2.7.3-debian-11-r0
+      image: docker.io/bitnami/airflow-worker:2.7.3-debian-11-r2
     - name: airflow
-      image: docker.io/bitnami/airflow:2.7.3-debian-11-r0
+      image: docker.io/bitnami/airflow:2.7.3-debian-11-r1
     - name: git
-      image: docker.io/bitnami/git:2.42.1-debian-11-r0
+      image: docker.io/bitnami/git:2.43.0-debian-11-r0
     - name: os-shell
-      image: docker.io/bitnami/os-shell:11-debian-11-r90
+      image: docker.io/bitnami/os-shell:11-debian-11-r91
   licenses: Apache-2.0
 apiVersion: v2
 appVersion: 2.7.3
@@ -50,4 +50,4 @@ maintainers:
 name: airflow
 sources:
 - https://github.com/bitnami/charts/tree/main/bitnami/airflow
-version: 16.1.2
+version: 16.1.5

charts/bitnami/airflow/README.md

@@ -1,6 +1,6 @@
 <!--- app-name: Apache Airflow -->
 
-# Apache Airflow packaged by Bitnami
+# Bitnami package for Apache Airflow
 
 Apache Airflow is a tool to express and execute workflows as directed acyclic graphs (DAGs). It includes utilities to schedule tasks, monitor task progress and handle task dependencies.
 
@@ -11,10 +11,10 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-helm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/airflow
+helm install my-release oci://registry-1.docker.io/bitnamicharts/airflow
 ```
 
-> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
+Looking to use Apache Airflow in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
 
 ## Introduction
 
@@ -22,8 +22,6 @@ This chart bootstraps an [Apache Airflow](https://github.com/bitnami/containers/
 
 Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
 
-Looking to use Apache Airflow in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
-
 ## Prerequisites
 
 - Kubernetes 1.23+
@@ -521,7 +519,7 @@ helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/airfl
 ```
 
 > Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
-> **Tip**: You can use the default [values.yaml](values.yaml)
+> **Tip**: You can use the default [values.yaml](https://github.com/bitnami/charts/tree/main/bitnami/airflow/values.yaml)
 
 ## Configuration and installation details
 

charts/bitnami/airflow/charts/postgresql/Chart.yaml

@@ -2,14 +2,14 @@ annotations:
   category: Database
   images: |
     - name: os-shell
-      image: docker.io/bitnami/os-shell:11-debian-11-r90
+      image: docker.io/bitnami/os-shell:11-debian-11-r91
     - name: postgres-exporter
-      image: docker.io/bitnami/postgres-exporter:0.15.0-debian-11-r0
+      image: docker.io/bitnami/postgres-exporter:0.15.0-debian-11-r2
     - name: postgresql
-      image: docker.io/bitnami/postgresql:16.0.0-debian-11-r15
+      image: docker.io/bitnami/postgresql:16.1.0-debian-11-r9
   licenses: Apache-2.0
 apiVersion: v2
-appVersion: 16.0.0
+appVersion: 16.1.0
 dependencies:
 - name: common
   repository: oci://registry-1.docker.io/bitnamicharts
@@ -34,4 +34,4 @@ maintainers:
 name: postgresql
 sources:
 - https://github.com/bitnami/charts/tree/main/bitnami/postgresql
-version: 13.2.2
+version: 13.2.15

charts/bitnami/airflow/charts/postgresql/README.md

@@ -1,6 +1,6 @@
 <!--- app-name: PostgreSQL -->
 
-# PostgreSQL packaged by Bitnami
+# Bitnami package for PostgreSQL
 
 PostgreSQL (Postgres) is an open source object-relational database known for reliability and data integrity. ACID-compliant, it supports foreign keys, joins, views, triggers and stored procedures.
 
@@ -11,10 +11,10 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-helm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/postgresql
+helm install my-release oci://registry-1.docker.io/bitnamicharts/postgresql
 ```
 
-> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
+Looking to use PostgreSQL in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
 
 ## Introduction
 
@@ -24,8 +24,6 @@ For HA, please see [this repo](https://github.com/bitnami/charts/tree/main/bitna
 
 Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
 
-Looking to use PostgreSQL in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
-
 ## Prerequisites
 
 - Kubernetes 1.23+
@@ -543,7 +541,7 @@ helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/postg
 ```
 
 > Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
-> **Tip**: You can use the default [values.yaml](values.yaml)
+> **Tip**: You can use the default [values.yaml](https://github.com/bitnami/charts/tree/main/bitnami/postgresql/values.yaml)
 
 ## Configuration and installation details
 

charts/bitnami/airflow/charts/postgresql/values.yaml

@@ -98,7 +98,7 @@ diagnosticMode:
 image:
   registry: docker.io
   repository: bitnami/postgresql
-  tag: 16.0.0-debian-11-r15
+  tag: 16.1.0-debian-11-r9
   digest: ""
   ## Specify a imagePullPolicy
   ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
@@ -1300,7 +1300,7 @@ volumePermissions:
   image:
     registry: docker.io
     repository: bitnami/os-shell
-    tag: 11-debian-11-r90
+    tag: 11-debian-11-r91
     digest: ""
     pullPolicy: IfNotPresent
     ## Optionally specify an array of imagePullSecrets.
@@ -1401,7 +1401,7 @@ metrics:
   image:
     registry: docker.io
     repository: bitnami/postgres-exporter
-    tag: 0.15.0-debian-11-r0
+    tag: 0.15.0-debian-11-r2
     digest: ""
     pullPolicy: IfNotPresent
     ## Optionally specify an array of imagePullSecrets.

charts/bitnami/airflow/charts/redis/Chart.yaml

@@ -2,13 +2,13 @@ annotations:
   category: Database
   images: |
     - name: os-shell
-      image: docker.io/bitnami/os-shell:11-debian-11-r90
+      image: docker.io/bitnami/os-shell:11-debian-11-r91
     - name: redis-exporter
-      image: docker.io/bitnami/redis-exporter:1.55.0-debian-11-r0
+      image: docker.io/bitnami/redis-exporter:1.55.0-debian-11-r2
     - name: redis-sentinel
-      image: docker.io/bitnami/redis-sentinel:7.2.3-debian-11-r0
+      image: docker.io/bitnami/redis-sentinel:7.2.3-debian-11-r1
     - name: redis
-      image: docker.io/bitnami/redis:7.2.3-debian-11-r0
+      image: docker.io/bitnami/redis:7.2.3-debian-11-r1
   licenses: Apache-2.0
 apiVersion: v2
 appVersion: 7.2.3
@@ -33,4 +33,4 @@ maintainers:
 name: redis
 sources:
 - https://github.com/bitnami/charts/tree/main/bitnami/redis
-version: 18.2.1
+version: 18.4.0

charts/bitnami/airflow/charts/redis/README.md

@@ -172,7 +172,7 @@ The command removes all the Kubernetes components associated with the chart and
 | `master.containerSecurityContext.allowPrivilegeEscalation` | Is it possible to escalate Redis® pod(s) privileges                                               | `false`                  |
 | `master.containerSecurityContext.seccompProfile.type`      | Set Redis® master containers' Security Context seccompProfile                                     | `RuntimeDefault`         |
 | `master.containerSecurityContext.capabilities.drop`        | Set Redis® master containers' Security Context capabilities to drop                               | `["ALL"]`                |
-| `master.kind`                                              | Use either Deployment or StatefulSet (default)                                                        | `StatefulSet`            |
+| `master.kind`                                              | Use either Deployment, StatefulSet (default) or DaemonSet                                             | `StatefulSet`            |
 | `master.schedulerName`                                     | Alternate scheduler for Redis® master pods                                                        | `""`                     |
 | `master.updateStrategy.type`                               | Redis® master statefulset strategy type                                                           | `RollingUpdate`          |
 | `master.minReadySeconds`                                   | How many seconds a pod needs to be ready before killing the next, during update                       | `0`                      |
@@ -237,6 +237,7 @@ The command removes all the Kubernetes components associated with the chart and
 
 | Name                                                        | Description                                                                                             | Value                    |
 | ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- | ------------------------ |
+| `replica.kind`                                              | Use either DaemonSet or StatefulSet (default)                                                           | `StatefulSet`            |
 | `replica.replicaCount`                                      | Number of Redis® replicas to deploy                                                                 | `3`                      |
 | `replica.configuration`                                     | Configuration for Redis® replicas nodes                                                             | `""`                     |
 | `replica.disableCommands`                                   | Array with Redis® commands to disable on replicas nodes                                             | `["FLUSHDB","FLUSHALL"]` |
@@ -363,7 +364,7 @@ The command removes all the Kubernetes components associated with the chart and
 | `sentinel.annotations`                                       | Additional custom annotations for Redis® Sentinel resource                                                                              | `{}`                             |
 | `sentinel.masterSet`                                         | Master set name                                                                                                                             | `mymaster`                       |
 | `sentinel.quorum`                                            | Sentinel Quorum                                                                                                                             | `2`                              |
-| `sentinel.getMasterTimeout`                                  | Amount of time to allow before get_sentinel_master_info() times out.                                                                        | `99`                             |
+| `sentinel.getMasterTimeout`                                  | Amount of time to allow before get_sentinel_master_info() times out.                                                                        | `90`                             |
 | `sentinel.automateClusterRecovery`                           | Automate cluster recovery in cases where the last replica is not considered a good replica and Sentinel won't automatically failover to it. | `false`                          |
 | `sentinel.redisShutdownWaitFailover`                         | Whether the Redis® master container waits for the failover at shutdown (in addition to the Redis® Sentinel container).              | `true`                           |
 | `sentinel.downAfterMilliseconds`                             | Timeout for detecting a Redis® node is down                                                                                             | `60000`                          |

charts/bitnami/airflow/charts/redis/templates/_helpers.tpl

@@ -44,7 +44,7 @@ Return sysctl image
 Return the proper Docker Image Registry Secret Names
 */}}
 {{- define "redis.imagePullSecrets" -}}
-{{- include "common.images.pullSecrets" (dict "images" (list .Values.image .Values.sentinel.image .Values.metrics.image .Values.volumePermissions.image .Values.sysctl.image) "global" .Values.global) -}}
+{{- include "common.images.renderPullSecrets" (dict "images" (list .Values.image .Values.sentinel.image .Values.metrics.image .Values.volumePermissions.image .Values.sysctl.image) "context" $) -}}
 {{- end -}}
 
 {{/*

charts/bitnami/airflow/charts/redis/templates/master/application.yaml

@@ -3,6 +3,7 @@ Copyright VMware, Inc.
 SPDX-License-Identifier: APACHE-2.0
 */}}
 
+{{- if gt (int64 .Values.master.count) 0 -}}
 {{- if or (not (eq .Values.architecture "replication")) (not .Values.sentinel.enabled) }}
 apiVersion: {{ include "common.capabilities.statefulset.apiVersion" . }}
 kind: {{ .Values.master.kind }}
@@ -15,7 +16,9 @@ metadata:
   annotations: {{- include "common.tplvalues.render" ( dict "value" .Values.commonAnnotations "context" $ ) | nindent 4 }}
   {{- end }}
 spec:
+  {{- if not (eq .Values.master.kind "DaemonSet") }}
   replicas: {{ .Values.master.count }}
+  {{- end }}
   {{- $podLabels := include "common.tplvalues.merge" ( dict "values" ( list .Values.master.podLabels .Values.commonLabels ) "context" . ) }}
   selector:
     matchLabels: {{- include "common.labels.matchLabels" ( dict "customLabels" $podLabels "context" $ ) | nindent 6 }}
@@ -471,7 +474,7 @@ spec:
         {{- if .Values.metrics.extraVolumes }}
         {{- include "common.tplvalues.render" ( dict "value" .Values.metrics.extraVolumes "context" $ ) | nindent 8 }}
         {{- end }}
-  {{- if not .Values.master.persistence.enabled }}
+  {{- if or (not .Values.master.persistence.enabled) (eq .Values.master.kind "DaemonSet") }}
         - name: redis-data
           {{- if or .Values.master.persistence.medium .Values.master.persistence.sizeLimit }}
           emptyDir:
@@ -526,3 +529,4 @@ spec:
         {{- include "common.storage.class" (dict "persistence" .Values.master.persistence "global" .Values.global) | nindent 8 }}
   {{- end }}
 {{- end }}
+{{- end }}

charts/bitnami/airflow/charts/redis/templates/master/service.yaml

@@ -3,7 +3,7 @@ Copyright VMware, Inc.
 SPDX-License-Identifier: APACHE-2.0
 */}}
 
-{{- if not .Values.sentinel.enabled }}
+{{- if and (not .Values.sentinel.enabled) (gt (int64 .Values.master.count) 0) }}
 apiVersion: v1
 kind: Service
 metadata:

charts/bitnami/airflow/charts/redis/templates/replicas/application.yaml

@@ -5,7 +5,7 @@ SPDX-License-Identifier: APACHE-2.0
 
 {{- if and (eq .Values.architecture "replication") (not .Values.sentinel.enabled) }}
 apiVersion: {{ include "common.capabilities.statefulset.apiVersion" . }}
-kind: StatefulSet
+kind: {{ .Values.replica.kind }}
 metadata:
   name: {{ printf "%s-replicas" (include "common.names.fullname" .) }}
   namespace: {{ .Release.Namespace | quote }}
@@ -15,14 +15,16 @@ metadata:
   annotations: {{- include "common.tplvalues.render" ( dict "value" .Values.commonAnnotations "context" $ ) | nindent 4 }}
   {{- end }}
 spec:
-  {{- if not .Values.replica.autoscaling.enabled }}
+  {{- if and (not (eq .Values.replica.kind "DaemonSet")) (not .Values.replica.autoscaling.enabled) }}
   replicas: {{ .Values.replica.replicaCount }}
   {{- end }}
   {{- $podLabels := include "common.tplvalues.merge" ( dict "values" ( list .Values.replica.podLabels .Values.commonLabels ) "context" . ) }}
   selector:
     matchLabels: {{- include "common.labels.matchLabels" ( dict "customLabels" $podLabels "context" $ ) | nindent 6 }}
       app.kubernetes.io/component: replica
+  {{- if (eq .Values.replica.kind "StatefulSet") }}
   serviceName: {{ printf "%s-headless" (include "common.names.fullname" .) }}
+  {{- end }}
   {{- if .Values.replica.updateStrategy }}
   updateStrategy: {{- toYaml .Values.replica.updateStrategy | nindent 4 }}
   {{- end }}
@@ -131,13 +133,19 @@ spec:
             - name: REDIS_REPLICATION_MODE
               value: replica
             - name: REDIS_MASTER_HOST
-            {{- if and (eq (int64 .Values.master.count) 1) (ne .Values.master.kind "Deployment") }}
+            {{- if .Values.replica.externalMaster.enabled }}
+              value: {{ .Values.replica.externalMaster.host | quote }}
+            {{- else if and (eq (int64 .Values.master.count) 1) (eq .Values.master.kind "StatefulSet") }}
               value: {{ template "common.names.fullname" . }}-master-0.{{ template "common.names.fullname" . }}-headless.{{ .Release.Namespace }}.svc.{{ .Values.clusterDomain }}
             {{- else }}
               value: {{ template "common.names.fullname" . }}-master.{{ .Release.Namespace }}.svc.{{ .Values.clusterDomain }}
             {{- end }}
             - name: REDIS_MASTER_PORT_NUMBER
+            {{- if .Values.replica.externalMaster.enabled }}
+              value: {{ .Values.replica.externalMaster.port | quote }}
+            {{- else }}
               value: {{ .Values.master.containerPorts.redis | quote }}
+            {{- end }}
             - name: ALLOW_EMPTY_PASSWORD
               value: {{ ternary "no" "yes" .Values.auth.enabled | quote }}
             {{- if .Values.auth.enabled }}
@@ -472,7 +480,7 @@ spec:
         {{- if .Values.metrics.extraVolumes }}
         {{- include "common.tplvalues.render" ( dict "value" .Values.metrics.extraVolumes "context" $ ) | nindent 8 }}
         {{- end }}
-  {{- if not .Values.replica.persistence.enabled }}
+  {{- if or (not .Values.replica.persistence.enabled) (not (eq .Values.replica.kind "StatefulSet")) }}
         - name: redis-data
           {{- if or .Values.replica.persistence.medium .Values.replica.persistence.sizeLimit }}
           emptyDir:

charts/bitnami/airflow/charts/redis/templates/scripts-configmap.yaml

@@ -109,7 +109,7 @@ data:
         fi
 
         info "about to run the command: $sentinel_info_command"
-        retry_while "eval $sentinel_info_command" 2 1
+        retry_while "eval $sentinel_info_command" 2 5
     }
 
     {{- if and .Values.replica.containerSecurityContext.runAsUser (eq (.Values.replica.containerSecurityContext.runAsUser | int) 0) }}
@@ -331,7 +331,7 @@ data:
             sentinel_info_command="{{- if and .Values.auth.enabled .Values.auth.sentinel }}REDISCLI_AUTH="\$REDIS_PASSWORD" {{ end }}timeout {{ .Values.sentinel.getMasterTimeout }} redis-cli -h $REDIS_SERVICE -p $SENTINEL_SERVICE_PORT sentinel get-master-addr-by-name {{ .Values.sentinel.masterSet }}"
         fi
         info "about to run the command: $sentinel_info_command"
-        retry_while "eval $sentinel_info_command" 2 1
+        retry_while "eval $sentinel_info_command" 2 5
     }
 
     [[ -f $REDIS_PASSWORD_FILE ]] && export REDIS_PASSWORD="$(< "${REDIS_PASSWORD_FILE}")"

charts/bitnami/airflow/charts/redis/values.schema.json

@@ -40,8 +40,8 @@
           "type": "string",
           "title": "Workload Kind",
           "form": true,
-          "description": "Allowed values: `Deployment` or `StatefulSet`",
+          "description": "Allowed values: `Deployment`, `StatefulSet` or `DaemonSet`",
-          "enum": ["Deployment", "StatefulSet"]
+          "enum": ["Deployment", "StatefulSet", "DaemonSet"]
         },
         "persistence": {
           "type": "object",
@@ -80,6 +80,13 @@
         "path": "architecture"
       },
       "properties": {
+        "kind": {
+          "type": "string",
+          "title": "Workload Kind",
+          "form": true,
+          "description": "Allowed values: `DaemonSet` or `StatefulSet`",
+          "enum": ["DaemonSet", "StatefulSet"]
+        },
         "replicaCount": {
           "type": "integer",
           "form": true,

charts/bitnami/airflow/charts/redis/values.yaml

@@ -91,7 +91,7 @@ diagnosticMode:
 image:
   registry: docker.io
   repository: bitnami/redis
-  tag: 7.2.3-debian-11-r0
+  tag: 7.2.3-debian-11-r1
   digest: ""
   ## Specify a imagePullPolicy
   ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
@@ -299,7 +299,7 @@ master:
     capabilities:
       drop:
         - ALL
-  ## @param master.kind Use either Deployment or StatefulSet (default)
+  ## @param master.kind Use either Deployment, StatefulSet (default) or DaemonSet
   ## ref: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/
   ##
   kind: StatefulSet
@@ -586,6 +586,10 @@ master:
 ##
 
 replica:
+  ## @param replica.kind Use either DaemonSet or StatefulSet (default)
+  ## ref: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/
+  ##
+  kind: StatefulSet
   ## @param replica.replicaCount Number of Redis® replicas to deploy
   ##
   replicaCount: 3
@@ -1056,7 +1060,7 @@ sentinel:
   image:
     registry: docker.io
     repository: bitnami/redis-sentinel
-    tag: 7.2.3-debian-11-r0
+    tag: 7.2.3-debian-11-r1
     digest: ""
     ## Specify a imagePullPolicy
     ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
@@ -1085,7 +1089,7 @@ sentinel:
   quorum: 2
   ## @param sentinel.getMasterTimeout Amount of time to allow before get_sentinel_master_info() times out.
   ##
-  getMasterTimeout: 99
+  getMasterTimeout: 90
   ## @param sentinel.automateClusterRecovery Automate cluster recovery in cases where the last replica is not considered a good replica and Sentinel won't automatically failover to it.
   ## This also prevents any new replica from starting until the last remaining replica is elected as master to guarantee that it is the one to be elected by Sentinel, and not a newly started replica with no data.
   ## NOTE: This feature requires a "downAfterMilliseconds" value less or equal to 2000.
@@ -1535,7 +1539,7 @@ metrics:
   image:
     registry: docker.io
     repository: bitnami/redis-exporter
-    tag: 1.55.0-debian-11-r0
+    tag: 1.55.0-debian-11-r2
     digest: ""
     pullPolicy: IfNotPresent
     ## Optionally specify an array of imagePullSecrets.
@@ -1847,7 +1851,7 @@ volumePermissions:
   image:
     registry: docker.io
     repository: bitnami/os-shell
-    tag: 11-debian-11-r90
+    tag: 11-debian-11-r91
     digest: ""
     pullPolicy: IfNotPresent
     ## Optionally specify an array of imagePullSecrets.
@@ -1895,7 +1899,7 @@ sysctl:
   image:
     registry: docker.io
     repository: bitnami/os-shell
-    tag: 11-debian-11-r90
+    tag: 11-debian-11-r91
     digest: ""
     pullPolicy: IfNotPresent
     ## Optionally specify an array of imagePullSecrets.

charts/bitnami/airflow/templates/_helpers.tpl

@@ -432,23 +432,21 @@ Gets the host to be used for this application.
 If not using ClusterIP, or if a host or LoadBalancerIP is not defined, the value will be empty.
 */}}
 {{- define "airflow.baseUrl" -}}
-{{- $host := "" -}}
+{{- $host := default (include "airflow.serviceIP" .) .Values.web.baseUrl -}}
-{{- $port := "" -}}
+{{- $port := printf ":%v" .Values.service.ports.http -}}
-{{- $servicePortString := printf "%v" .Values.service.ports.http -}}
+{{- $schema := "http://" -}}
-{{- if and (not (eq $servicePortString "80")) (not (eq $servicePortString "443")) -}}
+{{- if regexMatch "^https?://" .Values.web.baseUrl -}}
-  {{- $port = printf ":%s" $servicePortString -}}
+  {{- $schema = "" -}}
+{{- end -}}
+{{- if or (regexMatch ":\\d+$" .Values.web.baseUrl) (eq $port ":80") (eq $port ":443") -}}
+  {{- $port = "" -}}
+{{- end -}}
+{{- if and .Values.ingress.enabled .Values.ingress.hostname -}}
+  {{- $host = .Values.ingress.hostname -}}
 {{- end -}}
-{{- if .Values.ingress.enabled }}
-  {{- $host = .Values.ingress.hostname | default "" -}}
-{{- else -}}
-  {{- $host = .Values.web.baseUrl | default "" -}}
-{{- end }}
-{{- $host = default (include "airflow.serviceIP" .) $host -}}
 {{- if $host -}}
-  {{- printf "http://%s%s" $host $port -}}
+{{- printf "%s%s%s" $schema $host $port -}}
-{{- else -}}
+{{- end }}
-  {{- default "" .Values.web.baseUrl -}}
-{{- end -}}
 {{- end -}}
 
 {{/*

charts/bitnami/airflow/values.yaml

@@ -121,7 +121,7 @@ dags:
   image:
     registry: docker.io
     repository: bitnami/os-shell
-    tag: 11-debian-11-r90
+    tag: 11-debian-11-r91
     digest: ""
     pullPolicy: IfNotPresent
     ## Optionally specify an array of imagePullSecrets.
@@ -188,7 +188,7 @@ web:
   image:
     registry: docker.io
     repository: bitnami/airflow
-    tag: 2.7.3-debian-11-r0
+    tag: 2.7.3-debian-11-r1
     digest: ""
     ## Specify a imagePullPolicy
     ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
@@ -456,7 +456,7 @@ scheduler:
   image:
     registry: docker.io
     repository: bitnami/airflow-scheduler
-    tag: 2.7.3-debian-11-r0
+    tag: 2.7.3-debian-11-r1
     digest: ""
     ## Specify a imagePullPolicy
     ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
@@ -670,7 +670,7 @@ worker:
   image:
     registry: docker.io
     repository: bitnami/airflow-worker
-    tag: 2.7.3-debian-11-r0
+    tag: 2.7.3-debian-11-r2
     digest: ""
     ## Specify a imagePullPolicy
     ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
@@ -953,7 +953,7 @@ git:
   image:
     registry: docker.io
     repository: bitnami/git
-    tag: 2.42.1-debian-11-r0
+    tag: 2.43.0-debian-11-r0
     digest: ""
     ## Specify a imagePullPolicy
     ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'

charts/bitnami/cassandra/Chart.yaml

@@ -6,9 +6,9 @@ annotations:
   category: Database
   images: |
     - name: cassandra-exporter
-      image: docker.io/bitnami/cassandra-exporter:2.3.8-debian-11-r430
+      image: docker.io/bitnami/cassandra-exporter:2.3.8-debian-11-r431
     - name: cassandra
-      image: docker.io/bitnami/cassandra:4.1.3-debian-11-r75
+      image: docker.io/bitnami/cassandra:4.1.3-debian-11-r76
     - name: os-shell
       image: docker.io/bitnami/os-shell:11-debian-11-r91
   licenses: Apache-2.0
@@ -35,4 +35,4 @@ maintainers:
 name: cassandra
 sources:
 - https://github.com/bitnami/charts/tree/main/bitnami/cassandra
-version: 10.6.5
+version: 10.6.6

charts/bitnami/cassandra/README.md

@@ -1,6 +1,6 @@
 <!--- app-name: Apache Cassandra -->
 
-# Apache Cassandra packaged by Bitnami
+# Bitnami package for Apache Cassandra
 
 Apache Cassandra is an open source distributed database management system designed to handle large amounts of data across many servers, providing high availability with no single point of failure.
 
@@ -11,10 +11,10 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-helm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/cassandra
+helm install my-release oci://registry-1.docker.io/bitnamicharts/cassandra
 ```
 
-> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
+Looking to use Apache Cassandra in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
 
 ## Introduction
 
@@ -22,8 +22,6 @@ This chart bootstraps an [Apache Cassandra](https://github.com/bitnami/container
 
 Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
 
-Looking to use Apache Cassandra in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
-
 ## Prerequisites
 
 - Kubernetes 1.23+
@@ -317,7 +315,7 @@ helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/cassa
 ```
 
 > Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
-> **Tip**: You can use the default [values.yaml](values.yaml)
+> **Tip**: You can use the default [values.yaml](https://github.com/bitnami/charts/tree/main/bitnami/cassandra/values.yaml)
 
 ## Configuration and installation details
 

charts/bitnami/cassandra/values.yaml

@@ -76,7 +76,7 @@ diagnosticMode:
 image:
   registry: docker.io
   repository: bitnami/cassandra
-  tag: 4.1.3-debian-11-r75
+  tag: 4.1.3-debian-11-r76
   digest: ""
   ## Specify a imagePullPolicy
   ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
@@ -696,7 +696,7 @@ metrics:
   image:
     registry: docker.io
     repository: bitnami/cassandra-exporter
-    tag: 2.3.8-debian-11-r430
+    tag: 2.3.8-debian-11-r431
     digest: ""
     pullPolicy: IfNotPresent
     ## Optionally specify an array of imagePullSecrets.

charts/bitnami/kafka/Chart.lock

@@ -1,9 +1,9 @@
 dependencies:
 - name: zookeeper
   repository: oci://registry-1.docker.io/bitnamicharts
-  version: 12.3.1
+  version: 12.3.2
 - name: common
   repository: oci://registry-1.docker.io/bitnamicharts
   version: 2.13.3
-digest: sha256:1c5d16a6250c7bb9acafbd264e110b9e67dfd1500da17a98bacfb5622a596c26
+digest: sha256:36a6404578c8c05d0ca2d3bedefafbb22c339ba65472742fdeb35166e61650ca
-generated: "2023-11-07T09:36:31.291833258Z"
+generated: "2023-11-21T18:15:15.544843963Z"

charts/bitnami/kafka/Chart.yaml

@@ -6,15 +6,15 @@ annotations:
   category: Infrastructure
   images: |
     - name: jmx-exporter
-      image: docker.io/bitnami/jmx-exporter:0.20.0-debian-11-r0
+      image: docker.io/bitnami/jmx-exporter:0.20.0-debian-11-r1
     - name: kafka-exporter
-      image: docker.io/bitnami/kafka-exporter:1.7.0-debian-11-r132
+      image: docker.io/bitnami/kafka-exporter:1.7.0-debian-11-r133
     - name: kafka
-      image: docker.io/bitnami/kafka:3.6.0-debian-11-r1
+      image: docker.io/bitnami/kafka:3.6.0-debian-11-r2
     - name: kubectl
-      image: docker.io/bitnami/kubectl:1.28.3-debian-11-r0
+      image: docker.io/bitnami/kubectl:1.28.4-debian-11-r0
     - name: os-shell
-      image: docker.io/bitnami/os-shell:11-debian-11-r90
+      image: docker.io/bitnami/os-shell:11-debian-11-r91
   licenses: Apache-2.0
 apiVersion: v2
 appVersion: 3.6.0
@@ -45,4 +45,4 @@ maintainers:
 name: kafka
 sources:
 - https://github.com/bitnami/charts/tree/main/bitnami/kafka
-version: 26.4.1
+version: 26.4.2

charts/bitnami/kafka/README.md

@@ -1,6 +1,6 @@
 <!--- app-name: Apache Kafka -->
 
-# Apache Kafka packaged by Bitnami
+# Bitnami package for Apache Kafka
 
 Apache Kafka is a distributed streaming platform designed to build real-time pipelines and can be used as a message broker or as a replacement for a log aggregation solution for big data applications.
 
@@ -11,10 +11,10 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-helm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/kafka
+helm install my-release oci://registry-1.docker.io/bitnamicharts/kafka
 ```
 
-> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
+Looking to use Apache Kafka in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
 
 ## Introduction
 
@@ -22,8 +22,6 @@ This chart bootstraps a [Kafka](https://github.com/bitnami/containers/tree/main/
 
 Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
 
-Looking to use Apache Kafka in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
-
 ## Prerequisites
 
 - Kubernetes 1.23+
@@ -676,7 +674,7 @@ helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/kafka
 ```
 
 > Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
-> **Tip**: You can use the default [values.yaml](values.yaml)
+> **Tip**: You can use the default [values.yaml](https://github.com/bitnami/charts/tree/main/bitnami/kafka/values.yaml)
 
 ## Configuration and installation details
 

charts/bitnami/kafka/charts/zookeeper/Chart.lock

@@ -1,6 +1,6 @@
 dependencies:
 - name: common
   repository: oci://registry-1.docker.io/bitnamicharts
-  version: 2.13.2
+  version: 2.13.3
-digest: sha256:551ae9c020597fd0a1d62967d9899a3c57a12e92f49e7a3967b6a187efdcaead
+digest: sha256:9a971689db0c66ea95ac2e911c05014c2b96c6077c991131ff84f2982f88fb83
-generated: "2023-10-11T10:24:27.070886462Z"
+generated: "2023-11-08T15:19:54.720987032Z"

charts/bitnami/kafka/charts/zookeeper/Chart.yaml

@@ -26,4 +26,4 @@ maintainers:
 name: zookeeper
 sources:
 - https://github.com/bitnami/charts/tree/main/bitnami/zookeeper
-version: 12.3.1
+version: 12.3.2

charts/bitnami/kafka/charts/zookeeper/charts/common/Chart.yaml

@@ -2,7 +2,7 @@ annotations:
   category: Infrastructure
   licenses: Apache-2.0
 apiVersion: v2
-appVersion: 2.13.2
+appVersion: 2.13.3
 description: A Library Helm Chart for grouping common logic between bitnami charts.
   This chart is not deployable by itself.
 home: https://bitnami.com
@@ -20,4 +20,4 @@ name: common
 sources:
 - https://github.com/bitnami/charts
 type: library
-version: 2.13.2
+version: 2.13.3

charts/bitnami/kafka/charts/zookeeper/charts/common/README.md

@@ -34,8 +34,8 @@ Looking to use our applications in production? Try [VMware Application Catalog](
 
 ## Prerequisites
 
-- Kubernetes 1.19+
+- Kubernetes 1.23+
-- Helm 3.2.0+
+- Helm 3.8.0+
 
 ## Parameters
 

charts/bitnami/kafka/charts/zookeeper/charts/common/templates/_capabilities.tpl

@@ -184,7 +184,7 @@ Returns true if PodSecurityPolicy is supported
 {{/*
 Returns true if AdmissionConfiguration is supported
 */}}
-{{- define "common.capabilities.admisionConfiguration.supported" -}}
+{{- define "common.capabilities.admissionConfiguration.supported" -}}
 {{- if semverCompare ">=1.23-0" (include "common.capabilities.kubeVersion" .) -}}
   {{- true -}}
 {{- end -}}
@@ -193,7 +193,7 @@ Returns true if AdmissionConfiguration is supported
 {{/*
 Return the appropriate apiVersion for AdmissionConfiguration.
 */}}
-{{- define "common.capabilities.admisionConfiguration.apiVersion" -}}
+{{- define "common.capabilities.admissionConfiguration.apiVersion" -}}
 {{- if semverCompare "<1.23-0" (include "common.capabilities.kubeVersion" .) -}}
 {{- print "apiserver.config.k8s.io/v1alpha1" -}}
 {{- else if semverCompare "<1.25-0" (include "common.capabilities.kubeVersion" .) -}}

charts/bitnami/kafka/values.yaml

@@ -80,7 +80,7 @@ diagnosticMode:
 image:
   registry: docker.io
   repository: bitnami/kafka
-  tag: 3.6.0-debian-11-r1
+  tag: 3.6.0-debian-11-r2
   digest: ""
   ## Specify a imagePullPolicy
   ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
@@ -1328,7 +1328,7 @@ externalAccess:
     image:
       registry: docker.io
       repository: bitnami/kubectl
-      tag: 1.28.3-debian-11-r0
+      tag: 1.28.4-debian-11-r0
       digest: ""
       ## Specify a imagePullPolicy
       ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
@@ -1578,7 +1578,7 @@ volumePermissions:
   image:
     registry: docker.io
     repository: bitnami/os-shell
-    tag: 11-debian-11-r90
+    tag: 11-debian-11-r91
     digest: ""
     pullPolicy: IfNotPresent
     ## Optionally specify an array of imagePullSecrets.
@@ -1660,7 +1660,7 @@ metrics:
     image:
       registry: docker.io
       repository: bitnami/kafka-exporter
-      tag: 1.7.0-debian-11-r132
+      tag: 1.7.0-debian-11-r133
       digest: ""
       ## Specify a imagePullPolicy
       ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
@@ -1914,7 +1914,7 @@ metrics:
     image:
       registry: docker.io
       repository: bitnami/jmx-exporter
-      tag: 0.20.0-debian-11-r0
+      tag: 0.20.0-debian-11-r1
       digest: ""
       ## Specify a imagePullPolicy
       ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'

charts/bitnami/mariadb/Chart.yaml

@@ -37,4 +37,4 @@ maintainers:
 name: mariadb
 sources:
 - https://github.com/bitnami/charts/tree/main/bitnami/mariadb
-version: 14.1.3
+version: 14.1.4

charts/bitnami/mariadb/README.md

@@ -1,6 +1,6 @@
 <!--- app-name: MariaDB -->
 
-# MariaDB packaged by Bitnami
+# Bitnami package for MariaDB
 
 MariaDB is an open source, community-developed SQL database server that is widely in use around the world due to its enterprise features, flexibility, and collaboration with leading tech firms.
 

charts/bitnami/mysql/Chart.yaml

@@ -8,9 +8,9 @@ annotations:
     - name: mysql
       image: docker.io/bitnami/mysql:8.0.35-debian-11-r0
     - name: mysqld-exporter
-      image: docker.io/bitnami/mysqld-exporter:0.15.0-debian-11-r70
+      image: docker.io/bitnami/mysqld-exporter:0.15.0-debian-11-r71
     - name: os-shell
-      image: docker.io/bitnami/os-shell:11-debian-11-r90
+      image: docker.io/bitnami/os-shell:11-debian-11-r91
   licenses: Apache-2.0
 apiVersion: v2
 appVersion: 8.0.35
@@ -36,4 +36,4 @@ maintainers:
 name: mysql
 sources:
 - https://github.com/bitnami/charts/tree/main/bitnami/mysql
-version: 9.14.3
+version: 9.14.4

charts/bitnami/mysql/README.md

@@ -1,6 +1,6 @@
 <!--- app-name: MySQL -->
 
-# MySQL packaged by Bitnami
+# Bitnami package for MySQL
 
 MySQL is a fast, reliable, scalable, and easy to use open source relational database system. Designed to handle mission-critical, heavy-load production applications.
 
@@ -11,10 +11,10 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-helm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/mysql
+helm install my-release oci://registry-1.docker.io/bitnamicharts/mysql
 ```
 
-> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
+Looking to use MySQL in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
 
 ## Introduction
 
@@ -22,8 +22,6 @@ This chart bootstraps a [MySQL](https://github.com/bitnami/containers/tree/main/
 
 Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
 
-Looking to use MySQL in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
-
 ## Prerequisites
 
 - Kubernetes 1.23+
@@ -396,7 +394,7 @@ helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/mysql
 ```
 
 > Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
-> **Tip**: You can use the default [values.yaml](values.yaml)
+> **Tip**: You can use the default [values.yaml](https://github.com/bitnami/charts/tree/main/bitnami/mysql/values.yaml)
 
 ## Configuration and installation details
 
@@ -418,7 +416,7 @@ The allowed extensions are `.sh`, `.sql` and `.sql.gz`.
 
 These scripts are treated differently depending on their extension. While `.sh` scripts are executed on all the nodes, `.sql` and `.sql.gz` scripts are only executed on the primary nodes. This is because `.sh` scripts support conditional tests to identify the type of node they are running on, while such tests are not supported in `.sql` or `sql.gz` files.
 
-Refer to the [chart documentation for more information and a usage example](http://docs.bitnami.com/kubernetes/infrastructure/mysql/configuration/customize-new-instance/).
+Refer to the [chart documentation for more information and a usage example](https://docs.bitnami.com/kubernetes/infrastructure/mysql/configuration/customize-new-instance/).
 
 ### Sidecars and Init Containers
 

charts/bitnami/mysql/values.yaml

@@ -1039,7 +1039,7 @@ volumePermissions:
   image:
     registry: docker.io
     repository: bitnami/os-shell
-    tag: 11-debian-11-r90
+    tag: 11-debian-11-r91
     digest: ""
     pullPolicy: IfNotPresent
     ## Optionally specify an array of imagePullSecrets.
@@ -1073,7 +1073,7 @@ metrics:
   image:
     registry: docker.io
     repository: bitnami/mysqld-exporter
-    tag: 0.15.0-debian-11-r70
+    tag: 0.15.0-debian-11-r71
     digest: ""
     pullPolicy: IfNotPresent
     ## Optionally specify an array of imagePullSecrets.

charts/bitnami/postgresql/Chart.yaml

@@ -10,7 +10,7 @@ annotations:
     - name: postgres-exporter
       image: docker.io/bitnami/postgres-exporter:0.15.0-debian-11-r2
     - name: postgresql
-      image: docker.io/bitnami/postgresql:16.1.0-debian-11-r6
+      image: docker.io/bitnami/postgresql:16.1.0-debian-11-r9
   licenses: Apache-2.0
 apiVersion: v2
 appVersion: 16.1.0
@@ -38,4 +38,4 @@ maintainers:
 name: postgresql
 sources:
 - https://github.com/bitnami/charts/tree/main/bitnami/postgresql
-version: 13.2.12
+version: 13.2.15

charts/bitnami/postgresql/README.md

@@ -1,6 +1,6 @@
 <!--- app-name: PostgreSQL -->
 
-# PostgreSQL packaged by Bitnami
+# Bitnami package for PostgreSQL
 
 PostgreSQL (Postgres) is an open source object-relational database known for reliability and data integrity. ACID-compliant, it supports foreign keys, joins, views, triggers and stored procedures.
 

charts/bitnami/postgresql/values.yaml

@@ -98,7 +98,7 @@ diagnosticMode:
 image:
   registry: docker.io
   repository: bitnami/postgresql
-  tag: 16.1.0-debian-11-r6
+  tag: 16.1.0-debian-11-r9
   digest: ""
   ## Specify a imagePullPolicy
   ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'

charts/bitnami/spark/Chart.yaml

@@ -6,7 +6,7 @@ annotations:
   category: Infrastructure
   images: |
     - name: spark
-      image: docker.io/bitnami/spark:3.5.0-debian-11-r15
+      image: docker.io/bitnami/spark:3.5.0-debian-11-r16
   licenses: Apache-2.0
 apiVersion: v2
 appVersion: 3.5.0
@@ -30,4 +30,4 @@ maintainers:
 name: spark
 sources:
 - https://github.com/bitnami/charts/tree/main/bitnami/spark
-version: 8.1.5
+version: 8.1.6

charts/bitnami/spark/README.md

@@ -1,6 +1,6 @@
 <!--- app-name: Apache Spark -->
 
-# Apache Spark packaged by Bitnami
+# Bitnami package for Apache Spark
 
 Apache Spark is a high-performance engine for large-scale computing tasks, such as data processing, machine learning and real-time data streaming. It includes APIs for Java, Python, Scala and R.
 

charts/bitnami/spark/values.yaml

@@ -95,7 +95,7 @@ diagnosticMode:
 image:
   registry: docker.io
   repository: bitnami/spark
-  tag: 3.5.0-debian-11-r15
+  tag: 3.5.0-debian-11-r16
   digest: ""
   ## Specify a imagePullPolicy
   ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'

charts/bitnami/tomcat/Chart.yaml

@@ -10,7 +10,7 @@ annotations:
     - name: os-shell
       image: docker.io/bitnami/os-shell:11-debian-11-r91
     - name: tomcat
-      image: docker.io/bitnami/tomcat:10.1.16-debian-11-r0
+      image: docker.io/bitnami/tomcat:10.1.16-debian-11-r2
   licenses: Apache-2.0
 apiVersion: v2
 appVersion: 10.1.16
@@ -38,4 +38,4 @@ maintainers:
 name: tomcat
 sources:
 - https://github.com/bitnami/charts/tree/main/bitnami/tomcat
-version: 10.11.3
+version: 10.11.6

charts/bitnami/tomcat/README.md

@@ -1,6 +1,6 @@
 <!--- app-name: Apache Tomcat -->
 
-# Apache Tomcat packaged by Bitnami
+# Bitnami package for Apache Tomcat
 
 Apache Tomcat is an open-source web server designed to host and run Java-based web applications. It is a lightweight server with a good performance for applications running in production environments.
 
@@ -11,10 +11,10 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-helm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/tomcat
+helm install my-release oci://registry-1.docker.io/bitnamicharts/tomcat
 ```
 
-> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
+Looking to use Apache Tomcat in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
 
 ## Introduction
 
@@ -24,8 +24,6 @@ Tomcat implements several Java EE specifications including Java Servlet, JavaSer
 
 Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
 
-Looking to use Apache Tomcat in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
-
 ## Prerequisites
 
 - Kubernetes 1.23+
@@ -277,7 +275,7 @@ helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/tomca
 ```
 
 > Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
-> **Tip**: You can use the default [values.yaml](values.yaml)
+> **Tip**: You can use the default [values.yaml](https://github.com/bitnami/charts/tree/main/bitnami/tomcat/values.yaml)
 
 ## Configuration and installation details
 

charts/bitnami/tomcat/values.yaml

@@ -61,7 +61,7 @@ extraDeploy: []
 image:
   registry: docker.io
   repository: bitnami/tomcat
-  tag: 10.1.16-debian-11-r0
+  tag: 10.1.16-debian-11-r2
   digest: ""
   ## Specify a imagePullPolicy
   ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'

charts/bitnami/wordpress/Chart.lock

@@ -1,12 +1,12 @@
 dependencies:
 - name: memcached
   repository: oci://registry-1.docker.io/bitnamicharts
-  version: 6.7.0
+  version: 6.7.1
 - name: mariadb
   repository: oci://registry-1.docker.io/bitnamicharts
-  version: 14.1.1
+  version: 14.1.4
 - name: common
   repository: oci://registry-1.docker.io/bitnamicharts
   version: 2.13.3
-digest: sha256:ea092288db95be52ecf0389162c09783f7fba6d724d0e33aeb7f178b2f19a3c7
+digest: sha256:d6872ca9f6d3ba5637e0f7eba8e903cf7084034b65ded8009d5f9b623f20af4e
-generated: "2023-11-09T10:46:31.269080696Z"
+generated: "2023-11-21T23:55:03.718546053Z"

charts/bitnami/wordpress/Chart.yaml

@@ -10,7 +10,7 @@ annotations:
     - name: os-shell
       image: docker.io/bitnami/os-shell:11-debian-11-r91
     - name: wordpress
-      image: docker.io/bitnami/wordpress:6.4.1-debian-11-r4
+      image: docker.io/bitnami/wordpress:6.4.1-debian-11-r5
   licenses: Apache-2.0
 apiVersion: v2
 appVersion: 6.4.1
@@ -47,4 +47,4 @@ maintainers:
 name: wordpress
 sources:
 - https://github.com/bitnami/charts/tree/main/bitnami/wordpress
-version: 18.1.14
+version: 18.1.15

charts/bitnami/wordpress/README.md

@@ -1,6 +1,6 @@
 <!--- app-name: WordPress -->
 
-# WordPress packaged by Bitnami
+# Bitnami package for WordPress
 
 WordPress is the world's most popular blogging and content management platform. Powerful yet simple, everyone from students to global corporations use it to build beautiful, functional websites.
 
@@ -9,10 +9,10 @@ WordPress is the world's most popular blogging and content management platform.
 ## TL;DR
 
 ```console
-helm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/wordpress
+helm install my-release oci://registry-1.docker.io/bitnamicharts/wordpress
 ```
 
-> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
+Looking to use WordPress in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
 
 ## Introduction
 
@@ -22,8 +22,6 @@ It also packages the [Bitnami MariaDB chart](https://github.com/bitnami/charts/t
 
 Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
 
-Looking to use WordPress in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
-
 ## Prerequisites
 
 - Kubernetes 1.23+
@@ -396,7 +394,7 @@ helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/wordp
 ```
 
 > Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
-> **Tip**: You can use the default [values.yaml](values.yaml)
+> **Tip**: You can use the default [values.yaml](https://github.com/bitnami/charts/tree/main/bitnami/wordpress/values.yaml)
 
 ## Configuration and installation details
 

charts/bitnami/wordpress/charts/mariadb/Chart.yaml

@@ -2,14 +2,14 @@ annotations:
   category: Database
   images: |
     - name: mariadb
-      image: docker.io/bitnami/mariadb:11.1.2-debian-11-r1
+      image: docker.io/bitnami/mariadb:11.1.3-debian-11-r0
     - name: mysqld-exporter
-      image: docker.io/bitnami/mysqld-exporter:0.15.0-debian-11-r70
+      image: docker.io/bitnami/mysqld-exporter:0.15.0-debian-11-r71
     - name: os-shell
-      image: docker.io/bitnami/os-shell:11-debian-11-r90
+      image: docker.io/bitnami/os-shell:11-debian-11-r91
   licenses: Apache-2.0
 apiVersion: v2
-appVersion: 11.1.2
+appVersion: 11.1.3
 dependencies:
 - name: common
   repository: oci://registry-1.docker.io/bitnamicharts
@@ -33,4 +33,4 @@ maintainers:
 name: mariadb
 sources:
 - https://github.com/bitnami/charts/tree/main/bitnami/mariadb
-version: 14.1.1
+version: 14.1.4

charts/bitnami/wordpress/charts/mariadb/README.md

@@ -1,6 +1,6 @@
 <!--- app-name: MariaDB -->
 
-# MariaDB packaged by Bitnami
+# Bitnami package for MariaDB
 
 MariaDB is an open source, community-developed SQL database server that is widely in use around the world due to its enterprise features, flexibility, and collaboration with leading tech firms.
 
@@ -11,10 +11,10 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-helm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/mariadb
+helm install my-release oci://registry-1.docker.io/bitnamicharts/mariadb
 ```
 
-> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
+Looking to use MariaDB in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
 
 ## Introduction
 
@@ -24,8 +24,6 @@ MariaDB is developed as open source software and as a relational database it pro
 
 Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
 
-Looking to use MariaDB in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
-
 ## Prerequisites
 
 - Kubernetes 1.23+
@@ -412,7 +410,7 @@ helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/maria
 ```
 
 > Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
-> **Tip**: You can use the default [values.yaml](values.yaml)
+> **Tip**: You can use the default [values.yaml](https://github.com/bitnami/charts/tree/main/bitnami/mariadb/values.yaml)
 
 ## Configuration and installation details
 

charts/bitnami/wordpress/charts/mariadb/templates/servicemonitor.yaml

@@ -8,7 +8,7 @@ apiVersion: monitoring.coreos.com/v1
 kind: ServiceMonitor
 metadata:
   name: {{ include "common.names.fullname" . }}
-  namespace: {{ default .Release.Namespace .Values.metrics.prometheusRule.namespace | quote }}
+  namespace: {{ default .Release.Namespace .Values.metrics.serviceMonitor.namespace | quote }}
   {{- $labels := include "common.tplvalues.merge" ( dict "values" ( list .Values.metrics.serviceMonitor.labels .Values.commonLabels ) "context" . ) }}
   labels: {{- include "common.labels.standard" ( dict "customLabels" $labels "context" $ ) | nindent 4 }}
   {{- if .Values.commonAnnotations }}

charts/bitnami/wordpress/charts/mariadb/values.yaml

@@ -90,7 +90,7 @@ serviceBindings:
 image:
   registry: docker.io
   repository: bitnami/mariadb
-  tag: 11.1.2-debian-11-r1
+  tag: 11.1.3-debian-11-r0
   digest: ""
   ## Specify a imagePullPolicy
   ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
@@ -1016,7 +1016,7 @@ volumePermissions:
   image:
     registry: docker.io
     repository: bitnami/os-shell
-    tag: 11-debian-11-r90
+    tag: 11-debian-11-r91
     digest: ""
     pullPolicy: IfNotPresent
     ## Optionally specify an array of imagePullSecrets (secrets must be manually created in the namespace)
@@ -1052,7 +1052,7 @@ metrics:
   image:
     registry: docker.io
     repository: bitnami/mysqld-exporter
-    tag: 0.15.0-debian-11-r70
+    tag: 0.15.0-debian-11-r71
     digest: ""
     pullPolicy: IfNotPresent
     ## Optionally specify an array of imagePullSecrets (secrets must be manually created in the namespace)

charts/bitnami/wordpress/charts/memcached/Chart.yaml

@@ -2,11 +2,11 @@ annotations:
   category: Infrastructure
   images: |
     - name: memcached-exporter
-      image: docker.io/bitnami/memcached-exporter:0.13.0-debian-11-r121
+      image: docker.io/bitnami/memcached-exporter:0.13.0-debian-11-r122
     - name: memcached
-      image: docker.io/bitnami/memcached:1.6.22-debian-11-r0
+      image: docker.io/bitnami/memcached:1.6.22-debian-11-r1
     - name: os-shell
-      image: docker.io/bitnami/os-shell:11-debian-11-r90
+      image: docker.io/bitnami/os-shell:11-debian-11-r91
   licenses: Apache-2.0
 apiVersion: v2
 appVersion: 1.6.22
@@ -30,4 +30,4 @@ maintainers:
 name: memcached
 sources:
 - https://github.com/bitnami/charts/tree/main/bitnami/memcached
-version: 6.7.0
+version: 6.7.1

charts/bitnami/wordpress/charts/memcached/README.md

@@ -1,6 +1,6 @@
 <!--- app-name: Memcached -->
 
-# Memcached packaged by Bitnami
+# Bitnami package for Memcached
 
 Memcached is an high-performance, distributed memory object caching system, generic in nature, but intended for use in speeding up dynamic web applications by alleviating database load.
 
@@ -11,10 +11,10 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-helm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/memcached
+helm install my-release oci://registry-1.docker.io/bitnamicharts/memcached
 ```
 
-> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
+Looking to use Memcached in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
 
 ## Introduction
 
@@ -22,8 +22,6 @@ This chart bootstraps a [Memcached](https://github.com/bitnami/containers/tree/m
 
 Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
 
-Looking to use Memcached in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
-
 ## Prerequisites
 
 - Kubernetes 1.23+
@@ -296,7 +294,7 @@ helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/memca
 ```
 
 > Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
-> **Tip**: You can use the default [values.yaml](values.yaml)
+> **Tip**: You can use the default [values.yaml](https://github.com/bitnami/charts/tree/main/bitnami/memcached/values.yaml)
 
 ## Configuration and installation details
 

charts/bitnami/wordpress/charts/memcached/values.yaml

@@ -73,7 +73,7 @@ diagnosticMode:
 image:
   registry: docker.io
   repository: bitnami/memcached
-  tag: 1.6.22-debian-11-r0
+  tag: 1.6.22-debian-11-r1
   digest: ""
   ## Specify a imagePullPolicy
   ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
@@ -527,7 +527,7 @@ volumePermissions:
   image:
     registry: docker.io
     repository: bitnami/os-shell
-    tag: 11-debian-11-r90
+    tag: 11-debian-11-r91
     digest: ""
     pullPolicy: IfNotPresent
     ## Optionally specify an array of imagePullSecrets.
@@ -572,7 +572,7 @@ metrics:
   image:
     registry: docker.io
     repository: bitnami/memcached-exporter
-    tag: 0.13.0-debian-11-r121
+    tag: 0.13.0-debian-11-r122
     digest: ""
     pullPolicy: IfNotPresent
     ## Optionally specify an array of imagePullSecrets.

charts/bitnami/wordpress/values.yaml

@@ -76,7 +76,7 @@ diagnosticMode:
 image:
   registry: docker.io
   repository: bitnami/wordpress
-  tag: 6.4.1-debian-11-r4
+  tag: 6.4.1-debian-11-r5
   digest: ""
   ## Specify a imagePullPolicy
   ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'

charts/bitnami/zookeeper/Chart.yaml

@@ -6,9 +6,9 @@ annotations:
   category: Infrastructure
   images: |
     - name: os-shell
-      image: docker.io/bitnami/os-shell:11-debian-11-r90
+      image: docker.io/bitnami/os-shell:11-debian-11-r91
     - name: zookeeper
-      image: docker.io/bitnami/zookeeper:3.9.1-debian-11-r1
+      image: docker.io/bitnami/zookeeper:3.9.1-debian-11-r2
   licenses: Apache-2.0
 apiVersion: v2
 appVersion: 3.9.1
@@ -30,4 +30,4 @@ maintainers:
 name: zookeeper
 sources:
 - https://github.com/bitnami/charts/tree/main/bitnami/zookeeper
-version: 12.3.2
+version: 12.3.3

charts/bitnami/zookeeper/README.md

@@ -1,6 +1,6 @@
 <!--- app-name: Apache ZooKeeper -->
 
-# Apache ZooKeeper packaged by Bitnami
+# Bitnami package for Apache ZooKeeper
 
 Apache ZooKeeper provides a reliable, centralized register of configuration data and services for distributed applications.
 
@@ -11,10 +11,10 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 ## TL;DR
 
 ```console
-helm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/zookeeper
+helm install my-release oci://registry-1.docker.io/bitnamicharts/zookeeper
 ```
 
-> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
+Looking to use Apache ZooKeeper in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
 
 ## Introduction
 
@@ -22,8 +22,6 @@ This chart bootstraps a [ZooKeeper](https://github.com/bitnami/containers/tree/m
 
 Bitnami charts can be used with [Kubeapps](https://kubeapps.dev/) for deployment and management of Helm Charts in clusters.
 
-Looking to use Apache ZooKeeper in production? Try [VMware Tanzu Application Catalog](https://bitnami.com/enterprise), the enterprise edition of Bitnami Application Catalog.
-
 ## Prerequisites
 
 - Kubernetes 1.23+
@@ -342,7 +340,7 @@ helm install my-release -f values.yaml oci://REGISTRY_NAME/REPOSITORY_NAME/zooke
 ```
 
 > Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.
-> **Tip**: You can use the default [values.yaml](values.yaml)
+> **Tip**: You can use the default [values.yaml](https://github.com/bitnami/charts/tree/main/bitnami/zookeeper/values.yaml)
 
 ## Configuration and installation details
 

charts/bitnami/zookeeper/values.yaml

@@ -79,7 +79,7 @@ diagnosticMode:
 image:
   registry: docker.io
   repository: bitnami/zookeeper
-  tag: 3.9.1-debian-11-r1
+  tag: 3.9.1-debian-11-r2
   digest: ""
   ## Specify a imagePullPolicy
   ## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
@@ -678,7 +678,7 @@ volumePermissions:
   image:
     registry: docker.io
     repository: bitnami/os-shell
-    tag: 11-debian-11-r90
+    tag: 11-debian-11-r91
     digest: ""
     pullPolicy: IfNotPresent
     ## Optionally specify an array of imagePullSecrets.

charts/datadog/datadog/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Datadog changelog
 
+## 3.49.4
+
+* Exclude a namespace with Datadog resources from APM Single Step Instrumentation
+
+## 3.49.3
+
+* Fix NOTES warning for APM Instrumentation when apm.intrumentation.disabledNamespaces is set
+
+## 3.49.2
+
+* Fix check for APM Instrumentation when apm.intrumentation.disabledNamespaces is set 
+
+## 3.49.1
+
+* Update `fips.image.tag` to `1.0.0`
+
 ## 3.49.0
 
 * Beta: Add `datadog.apm.instrumentation` section to configure APM Single Step Instrumentation

charts/datadog/datadog/Chart.yaml

@@ -19,4 +19,4 @@ name: datadog
 sources:
 - https://app.datadoghq.com/account/settings#agent/kubernetes
 - https://github.com/DataDog/datadog-agent
-version: 3.49.0
+version: 3.49.4

charts/datadog/datadog/README.md

@@ -1,6 +1,6 @@
 # Datadog
 
-![Version: 3.49.0](https://img.shields.io/badge/Version-3.49.0-informational?style=flat-square) ![AppVersion: 7](https://img.shields.io/badge/AppVersion-7-informational?style=flat-square)
+![Version: 3.49.4](https://img.shields.io/badge/Version-3.49.4-informational?style=flat-square) ![AppVersion: 7](https://img.shields.io/badge/AppVersion-7-informational?style=flat-square)
 
 [Datadog](https://www.datadoghq.com/) is a hosted infrastructure monitoring platform. This chart adds the Datadog Agent to all nodes in your cluster via a DaemonSet. It also optionally depends on the [kube-state-metrics chart](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-state-metrics). For more information about monitoring Kubernetes with Datadog, please refer to the [Datadog documentation website](https://docs.datadoghq.com/agent/basic_agent_usage/kubernetes/).
 
@@ -816,7 +816,7 @@ helm install <RELEASE_NAME> \
 | fips.image.name | string | `"fips-proxy"` |  |
 | fips.image.pullPolicy | string | `"IfNotPresent"` | Datadog the FIPS sidecar image pull policy |
 | fips.image.repository | string | `nil` | Override default registry + image.name for the FIPS sidecar container. |
-| fips.image.tag | string | `"0.6.1"` | Define the FIPS sidecar container version to use. |
+| fips.image.tag | string | `"1.0.0"` | Define the FIPS sidecar container version to use. |
 | fips.local_address | string | `"127.0.0.1"` | Set local IP address |
 | fips.port | int | `9803` | Specifies which port is used by the containers to communicate to the FIPS sidecar. |
 | fips.portRange | int | `15` | Specifies the number of ports used, defaults to 13 https://github.com/DataDog/datadog-agent/blob/7.44.x/pkg/config/config.go#L1564-L1577 |

charts/datadog/datadog/templates/NOTES.txt

@@ -176,13 +176,13 @@ APM Single Step Instrumentation will be enabled in the whole cluster.
 
 {{- end }}
 
-{{- if and .Values.datadog.apm.instrumentation.disabled_namespaces (eq .Values.datadog.apm.instrumentation.enabled "false") }}
+{{- if and .Values.datadog.apm.instrumentation.disabled_namespaces (not .Values.datadog.apm.instrumentation.enabled) }}
 
 #################################################################
 ####               WARNING: Configuration notice             ####
 #################################################################
 
-The option `datadog.apm.instrumentation.enabled_namespaces` is set while `datadog.apm.instrumentation.enabled` is disabled.
+The option `datadog.apm.instrumentation.disabled_namespaces` is set while `datadog.apm.instrumentation.enabled` is disabled.
 APM Single Step Instrumentation will be disabled in the whole cluster.
 
 {{- end }}

charts/datadog/datadog/templates/_helpers.tpl

@@ -893,3 +893,35 @@ Create RBACs for custom resources
     false
   {{- end -}}
 {{- end -}}
+
+{{/*
+Return all namespaces with enabled Single Step Instrumentation. If instrumentation.enabledNamespaces contains the namespace where Datadog is installed,
+it will be removed.
+*/}}
+{{- define "apmInstrumentation.enabledNamespaces" -}}
+{{- if and .Values.datadog.apm .Values.datadog.apm.instrumentation -}}
+{{- if and .Values.datadog.apm.instrumentation.enabledNamespaces (not .Values.datadog.apm.instrumentation.enabled) -}}
+{{- if has .Release.Namespace .Values.datadog.apm.instrumentation.enabledNamespaces -}}
+{{- $ns := mustWithout .Values.datadog.apm.instrumentation.enabledNamespaces .Release.Namespace -}}
+{{- if $ns -}}
+{{- $ns | toJson | quote -}}
+{{- end -}}
+{{- else -}}
+{{- .Values.datadog.apm.instrumentation.enabledNamespaces | toJson | quote -}}
+{{- end -}}
+{{- end -}}
+{{- end -}}
+{{- end -}}
+
+{{/*
+Return all namespaces with disabled Single Step Instrumentation
+*/}}
+{{- define "apmInstrumentation.disabledNamespaces" -}}
+{{- if and .Values.datadog.apm .Values.datadog.apm.instrumentation -}}
+{{- if and .Values.datadog.apm.instrumentation.disabledNamespaces .Values.datadog.apm.instrumentation.enabled -}}
+{{- append .Values.datadog.apm.instrumentation.disabledNamespaces .Release.Namespace | toJson | quote  -}}
+{{- else if .Values.datadog.apm.instrumentation.enabled -}}
+{{- list .Release.Namespace | toJson | quote -}}
+{{- end -}}
+{{- end -}}
+{{- end -}}

charts/datadog/datadog/templates/cluster-agent-deployment.yaml

@@ -236,17 +236,17 @@ spec:
           {{- end }}
           - name: DD_REMOTE_CONFIGURATION_ENABLED
             value: {{ include "clusterAgent-remoteConfiguration-enabled" . | quote }}
-                    {{- if .Values.datadog.apm.instrumentation.enabled }}
+          {{- if .Values.datadog.apm.instrumentation.enabled }}
           - name: DD_APM_INSTRUMENTATION_ENABLED
             value: "true"
           {{- end }}
-          {{- if .Values.datadog.apm.instrumentation.enabledNamespaces }}
+          {{- if ne (include "apmInstrumentation.enabledNamespaces" .) "" }}
           - name: DD_APM_INSTRUMENTATION_ENABLED_NAMESPACES
-            value: {{ .Values.datadog.apm.instrumentation.enabledNamespaces | toJson | quote }}
+            value: {{ include "apmInstrumentation.enabledNamespaces" . }}
           {{- end }}
-          {{- if .Values.datadog.apm.instrumentation.disabledNamespaces }}
+          {{- if ne (include "apmInstrumentation.disabledNamespaces" .) "" }}
           - name: DD_APM_INSTRUMENTATION_DISABLED_NAMESPACES
-            value: {{ .Values.datadog.apm.instrumentation.disabledNamespaces | toJson | quote }}
+            value: {{ include "apmInstrumentation.disabledNamespaces" . }}
           {{- end }}
           {{- if .Values.datadog.apm.instrumentation.libVersions }}
           - name: DD_APM_INSTRUMENTATION_LIB_VERSIONS

charts/datadog/datadog/values.yaml

@@ -1259,7 +1259,7 @@ fips:
     name: fips-proxy
 
     # fips.image.tag -- Define the FIPS sidecar container version to use.
-    tag: 0.6.1
+    tag: 1.0.0
 
     # fips.image.pullPolicy -- Datadog the FIPS sidecar image pull policy
     pullPolicy: IfNotPresent

charts/haproxy/haproxy/Chart.yaml

@@ -1,8 +1,6 @@
 annotations:
   artifacthub.io/changes: |
-    - Use Ingress Controller 1.10.10 version for base image
+    - CRD job updates and bug fixes
-    - Add CRD install/upgrade job for automated CRD management
-    - Remove default CRDs provided by Chart
   catalog.cattle.io/certified: partner
   catalog.cattle.io/display-name: HAProxy Kubernetes Ingress Controller
   catalog.cattle.io/kube-version: '>=1.22.0-0'
@@ -23,4 +21,4 @@ name: haproxy
 sources:
 - https://github.com/haproxytech/kubernetes-ingress
 type: application
-version: 1.35.0
+version: 1.35.1

charts/haproxy/haproxy/README.md

@@ -246,6 +246,16 @@ helm install keda kedacore/keda --namespace keda
 helm install mytest haproxytech/kubernetes-ingress -f mykeda.yaml
 ```
 
+## Installing on Azure Managed Kubernetes Service (AKS)
+
+By default Azure LB sends probe to `/` and expects HTTP status codes of 200-399 to consider Pod healthy, which means probes end up on default HTTP backend returning HTTP 404 status code. Since v1.20 AKS service annotation `service.beta.kubernetes.io/azure-load-balancer-health-probe-request-path` can be used to override health probe behaviour and we recommend using the following annotation on AKS to target `/healthz` endpoint for health probes:
+
+```console
+helm install ...
+  --set controller.service.type=LoadBalancer \
+  --set controller.service.annotations."service\.beta\.kubernetes\.io/azure-load-balancer-health-probe-request-path"=/healthz
+```
+
 ## Upgrading the chart
 
 To upgrade the _my-release_ deployment:

charts/haproxy/haproxy/templates/controller-crdjob.yaml

@@ -20,16 +20,20 @@ metadata:
   name: {{ include "kubernetes-ingress.crdjob.fullname" . }}
   namespace: {{ include "kubernetes-ingress.namespace" . }}
   labels:
-    app.kubernetes.io/name: {{ include "kubernetes-ingress.name" . }}
+    app.kubernetes.io/name: {{ include "kubernetes-ingress.crdjob.fullname" . }}
     helm.sh/chart: {{ include "kubernetes-ingress.chart" . }}
     app.kubernetes.io/managed-by: {{ .Release.Service }}
     app.kubernetes.io/instance: {{ .Release.Name }}
     app.kubernetes.io/version: {{ .Chart.AppVersion }}
 spec:
+{{- if .Capabilities.APIVersions.Has "batch/v1alpha1" }}
+  ttlSecondsAfterFinished: 0
+{{- end }}
+  backoffLimit: 0
   template:
     metadata:
       labels:
-        app.kubernetes.io/name: {{ include "kubernetes-ingress.name" . }}
+        app.kubernetes.io/name: {{ include "kubernetes-ingress.crdjob.fullname" . }}
         app.kubernetes.io/instance: {{ .Release.Name }}
         {{- if .Values.controller.podLabels }}
 {{ toYaml .Values.controller.podLabels | indent 8 }}
@@ -39,13 +43,63 @@ spec:
 {{ toYaml .Values.controller.podAnnotations | indent 8 }}
       {{- end }}
     spec:
+      restartPolicy: Never
       serviceAccountName: {{ include "kubernetes-ingress.serviceAccountName" . }}
+{{- if .Values.controller.imageCredentials.registry }}
+      imagePullSecrets:
+      - name: {{ include "kubernetes-ingress.fullname" . }}
+{{- else if .Values.controller.existingImagePullSecret }}
+      imagePullSecrets:
+      - name: {{ .Values.controller.existingImagePullSecret }}
+{{- end }}
+{{- if .Values.controller.priorityClassName }}
+      priorityClassName: {{ .Values.controller.priorityClassName }}
+{{- end }}
+{{- if .Values.controller.runtimeClassName }}
+      runtimeClassName: {{ .Values.controller.runtimeClassName }}
+{{- end }}
+{{- if .Values.controller.unprivileged }}
+      securityContext:
+        runAsNonRoot: true
+        runAsUser:  1000
+        runAsGroup: 1000
+{{- end }}
       containers:
-        - name: {{ include "kubernetes-ingress.name" . }}-{{ .Values.controller.name }}
+        - name: crd
           image: "{{ .Values.controller.image.repository }}:{{ tpl .Values.controller.image.tag . }}"
           imagePullPolicy: {{ .Values.controller.image.pullPolicy }}
           command:
             - /haproxy-ingress-controller
             - --job-check-crd
-      restartPolicy: Never
+          {{- if .Values.controller.unprivileged }}
-  backoffLimit: 0
+          securityContext:
+            runAsNonRoot: true
+            runAsUser:  1000
+            runAsGroup: 1000
+            allowPrivilegeEscalation: {{ .Values.controller.allowPrivilegeEscalation }}
+            capabilities:
+              drop:
+                - ALL
+              add:
+                - NET_BIND_SERVICE
+            {{- if .Values.controller.enableRuntimeDefaultSeccompProfile }}
+            seccompProfile:
+              type: RuntimeDefault
+            {{- end }}
+          {{- end }}
+      {{- with.Values.controller.initContainers }}
+      initContainers:
+          {{- toYaml . | nindent 8 }}
+      {{- end }}
+      {{- with .Values.controller.nodeSelector }}
+      nodeSelector:
+        {{- toYaml . | nindent 8 }}
+      {{- end }}
+      {{- with .Values.controller.affinity }}
+      affinity:
+        {{- toYaml . | nindent 8 }}
+      {{- end }}
+      {{- with .Values.controller.tolerations }}
+      tolerations:
+        {{- toYaml . | nindent 8 }}
+      {{- end }}

charts/jenkins/jenkins/CHANGELOG.md

@@ -12,11 +12,14 @@ Use the following links to reference issues, PRs, and commits prior to v2.6.0.
 The changelog until v1.5.7 was auto-generated based on git commits.
 Those entries include a reference to the git commit to be able to get more details.
 
+## 4.8.4
+
+Add `artifacthub.io/changes` changelog annotation to the released chart.
+
 ## 4.8.3
 
 Update Jenkins image and appVersion to jenkins lts release version 2.426.1
 
-
 ## 4.8.2
 
 Add the ability to modify `retentionTimeout` and `waitForPodSec` default value in JCasC

charts/jenkins/jenkins/Chart.yaml

@@ -1,5 +1,7 @@
 annotations:
   artifacthub.io/category: integration-delivery
+  artifacthub.io/changes: Add `artifacthub.io/changes` changelog annotation to the
+    released chart.
   artifacthub.io/images: |
     - name: jenkins
       image: jenkins/jenkins:2.426.1-jdk11
@@ -49,4 +51,4 @@ sources:
 - https://github.com/jenkinsci/docker-inbound-agent
 - https://github.com/maorfr/kube-tasks
 - https://github.com/jenkinsci/configuration-as-code-plugin
-version: 4.8.3
+version: 4.8.4

charts/jfrog/artifactory-ha/CHANGELOG.md

@@ -1,9 +1,10 @@
 # JFrog Artifactory-ha Chart Changelog
 All changes to this chart will be documented in this file
 
-## [107.71.4] - Oct 31, 2023
+## [107.71.5] - Nov 15, 2023
 * Fixed - StatefulSet pod annotations changed from range to toYaml [GH-1828](https://github.com/jfrog/charts/issues/1828)
-* Fixed - Invalid format for awsS3V3 `multiPartLimit,multipartElementSize` in binarystore.xml.
+* Fixed - Invalid format for awsS3V3 `multiPartLimit,multipartElementSize` in binarystore.xml
+* Fixed - Artifactory primary service condition
 
 ## [107.69.0] - Sep 18, 2023
 * Adjust rtfs context

charts/jfrog/artifactory-ha/Chart.yaml

@@ -4,7 +4,7 @@ annotations:
   catalog.cattle.io/kube-version: '>= 1.14.0-0'
   catalog.cattle.io/release-name: artifactory-ha
 apiVersion: v2
-appVersion: 7.71.4
+appVersion: 7.71.5
 dependencies:
 - condition: postgresql.enabled
   name: postgresql
@@ -26,4 +26,4 @@ name: artifactory-ha
 sources:
 - https://github.com/jfrog/charts
 type: application
-version: 107.71.4
+version: 107.71.5

charts/jfrog/artifactory-ha/templates/artifactory-primary-service.yaml

@@ -1,4 +1,4 @@
-{{- if gt (.Values.artifactory.node.replicaCount | int) 0  -}}
+{{- if gt (.Values.artifactory.primary.replicaCount | int) 0  -}}
 # Internal service for Artifactory primary node only!
 # Used by member nodes to check readiness of primary node before starting up
 apiVersion: v1

charts/jfrog/artifactory-jcr/CHANGELOG.md

@@ -1,7 +1,7 @@
 # JFrog Container Registry Chart Changelog
 All changes to this chart will be documented in this file.
 
-## [107.71.4] - Jul 20, 2023
+## [107.71.5] - Jul 20, 2023
 * Disabled federation services when splitServicesToContainers=true
 
 ## [107.45.0] - Aug 25, 2022

charts/jfrog/artifactory-jcr/Chart.yaml

@@ -4,11 +4,11 @@ annotations:
   catalog.cattle.io/kube-version: '>= 1.14.0-0'
   catalog.cattle.io/release-name: artifactory-jcr
 apiVersion: v2
-appVersion: 7.71.4
+appVersion: 7.71.5
 dependencies:
 - name: artifactory
   repository: file://./charts/artifactory
-  version: 107.71.4
+  version: 107.71.5
 description: JFrog Container Registry
 home: https://jfrog.com/container-registry/
 icon: https://raw.githubusercontent.com/jfrog/charts/ea5c3112c24a973f64f3ccd99747323db292a369/stable/artifactory-jcr/logo/jcr-logo.png
@@ -27,4 +27,4 @@ name: artifactory-jcr
 sources:
 - https://github.com/jfrog/charts
 type: application
-version: 107.71.4
+version: 107.71.5

charts/jfrog/artifactory-jcr/charts/artifactory/CHANGELOG.md

@@ -1,7 +1,7 @@
 # JFrog Artifactory Chart Changelog
 All changes to this chart will be documented in this file.
 
-## [107.71.4] - Oct 31, 2023
+## [107.71.5] - Oct 31, 2023
 * Fixed - StatefulSet pod annotations changed from range to toYaml [GH-1828](https://github.com/jfrog/charts/issues/1828)
 * Fixed - Invalid format for awsS3V3 `multiPartLimit,multipartElementSize` in binarystore.xml.
 

charts/jfrog/artifactory-jcr/charts/artifactory/Chart.yaml

@@ -1,5 +1,5 @@
 apiVersion: v2
-appVersion: 7.71.4
+appVersion: 7.71.5
 dependencies:
 - condition: postgresql.enabled
   name: postgresql
@@ -21,4 +21,4 @@ name: artifactory
 sources:
 - https://github.com/jfrog/charts
 type: application
-version: 107.71.4
+version: 107.71.5

charts/new-relic/nri-bundle/Chart.lock

@@ -1,7 +1,7 @@
 dependencies:
 - name: newrelic-infrastructure
   repository: https://newrelic.github.io/nri-kubernetes
-  version: 3.25.0
+  version: 3.26.0
 - name: nri-prometheus
   repository: https://newrelic.github.io/nri-prometheus
   version: 2.1.17
@@ -10,7 +10,7 @@ dependencies:
   version: 1.7.0
 - name: nri-metadata-injection
   repository: https://newrelic.github.io/k8s-metadata-injection
-  version: 4.14.0
+  version: 4.14.1
 - name: newrelic-k8s-metrics-adapter
   repository: https://newrelic.github.io/newrelic-k8s-metrics-adapter
   version: 1.6.0
@@ -19,7 +19,7 @@ dependencies:
   version: 5.12.1
 - name: nri-kube-events
   repository: https://newrelic.github.io/nri-kube-events
-  version: 3.4.0
+  version: 3.5.0
 - name: newrelic-logging
   repository: https://newrelic.github.io/helm-charts
   version: 1.18.1
@@ -31,6 +31,6 @@ dependencies:
   version: 0.1.4
 - name: newrelic-infra-operator
   repository: https://newrelic.github.io/newrelic-infra-operator
-  version: 2.5.0
+  version: 2.6.0
-digest: sha256:b48bc300997722fa6fdf7e0d5ceaaf9e48c7dc4d7d22d91239bfd2ccd293bb93
+digest: sha256:72573c55a0ffa6b4756c19e15f0b6f53bb1ad6fcc47197b08c842f8fc893c392
-generated: "2023-11-14T01:57:00.704416878Z"
+generated: "2023-11-21T05:20:45.737726359Z"

charts/new-relic/nri-bundle/Chart.yaml

@@ -7,7 +7,7 @@ dependencies:
 - condition: infrastructure.enabled,newrelic-infrastructure.enabled
   name: newrelic-infrastructure
   repository: file://./charts/newrelic-infrastructure
-  version: 3.25.0
+  version: 3.26.0
 - condition: prometheus.enabled,nri-prometheus.enabled
   name: nri-prometheus
   repository: file://./charts/nri-prometheus
@@ -19,7 +19,7 @@ dependencies:
 - condition: webhook.enabled,nri-metadata-injection.enabled
   name: nri-metadata-injection
   repository: file://./charts/nri-metadata-injection
-  version: 4.14.0
+  version: 4.14.1
 - condition: metrics-adapter.enabled,newrelic-k8s-metrics-adapter.enabled
   name: newrelic-k8s-metrics-adapter
   repository: file://./charts/newrelic-k8s-metrics-adapter
@@ -31,7 +31,7 @@ dependencies:
 - condition: kubeEvents.enabled,nri-kube-events.enabled
   name: nri-kube-events
   repository: file://./charts/nri-kube-events
-  version: 3.4.0
+  version: 3.5.0
 - condition: logging.enabled,newrelic-logging.enabled
   name: newrelic-logging
   repository: file://./charts/newrelic-logging
@@ -48,7 +48,7 @@ dependencies:
 - condition: newrelic-infra-operator.enabled
   name: newrelic-infra-operator
   repository: file://./charts/newrelic-infra-operator
-  version: 2.5.0
+  version: 2.6.0
 description: Groups together the individual charts for the New Relic Kubernetes solution
   for a more comfortable deployment.
 home: https://github.com/newrelic/helm-charts
@@ -89,4 +89,4 @@ sources:
 - https://github.com/newrelic/helm-charts/tree/master/charts/newrelic-logging
 - https://github.com/newrelic/helm-charts/tree/master/charts/newrelic-pixie
 - https://github.com/newrelic/newrelic-infra-operator/tree/master/charts/newrelic-infra-operator
-version: 5.0.45
+version: 5.0.46

charts/new-relic/nri-bundle/charts/newrelic-infra-operator/Chart.yaml

@@ -1,5 +1,5 @@
 apiVersion: v2
-appVersion: 0.13.0
+appVersion: 0.14.0
 dependencies:
 - name: common-library
   repository: https://helm-charts.newrelic.com
@@ -32,4 +32,4 @@ name: newrelic-infra-operator
 sources:
 - https://github.com/newrelic/newrelic-infra-operator
 - https://github.com/newrelic/newrelic-infra-operator/tree/main/charts/newrelic-infra-operator
-version: 2.5.0
+version: 2.6.0