* [bitnami/redis] Fix sentinel.conf generated when sentinel.externalAccess is enabled
With externalAccess enabled, start-sentinel.sh pinned "sentinel monitor" to
the first external address and wrote known-replica and known-sentinel entries
for every node, including the master and the Sentinel itself. When the master
happened to be the first address, a restarted Sentinel found the master in
its own replica list, sent REPLICAOF pointing at the master's own address,
and the cluster lost its master. Apply the same guards the headless path
already uses and keep the first-address fallback for the initial deployment.
Signed-off-by: Seonghae Jo <seonghae.jo@navercorp.com>
* Update CHANGELOG.md
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
---------
Signed-off-by: Seonghae Jo <seonghae.jo@navercorp.com>
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
Co-authored-by: Bitnami Bot <bitnami.bot@broadcom.com>
* Refactor host_id function to include namespace
Using only hostname for host_id() will cause multiple sentinels in different namespaces with the same fullnameOverride have the same SENTINEL MYIDs, which can cause multiple replica clusters to merge into one.
Signed-off-by: laorient <rong__zhou@hotmail.com>
* [bitnami/redis] Bump version
Signed-off-by: Jota Martos <jota.martos@broadcom.com>
---------
Signed-off-by: laorient <rong__zhou@hotmail.com>
Signed-off-by: Jota Martos <jota.martos@broadcom.com>
Co-authored-by: Jota Martos <jota.martos@broadcom.com>
* [bitnami/postgresql] Add primary.replicaCount to allow scaling the primary to zero
Setting it to 0 can be useful in non-production environments to save
costs by scaling down idle components without deleting the
StatefulSet or its PersistentVolumeClaim.
Signed-off-by: Claudio Netto <nettinhorama@gmail.com>
* [bitnami/postgresql] Restrict primary.replicaCount to 0 or 1
A PostgreSQL primary cannot be horizontally scaled the way
readReplicas can, so constrain it via values.schema.json.
Signed-off-by: Claudio Netto <nettinhorama@gmail.com>
* [bitnami/postgresql] Clarify primary.replicaCount description
Note the 0-or-1 restriction directly in the field description instead
of only in values.schema.json.
Signed-off-by: Claudio Netto <nettinhorama@gmail.com>
* Force CI reload
ai-assisted=no
---------
Signed-off-by: Claudio Netto <nettinhorama@gmail.com>
Co-authored-by: Gonzalo Gomez Gracia <gonzalo.gomez@broadcom.com>
* Allow overriding individual fields of updateStrategy
The current style doesn't give subcharts the option to nullify fields within updateStrategy. So the following isn't possible in a subchart's Value.yaml:
```yaml
updateStrategy:
type: OnDelete
rollingUpdate: null
```
Without the null, I get an error that the updateStrategy OnDelete doesn't allow a non-null value for rollingUpdate.
Signed-off-by: jkohenpdt <jkohen@pdtpartners.com>
* Bumped chart version
Signed-off-by: jkohenpdt <jkohen@pdtpartners.com>
* Trigger actions
Signed-off-by: Jota Martos <jota.martos@broadcom.com>
---------
Signed-off-by: jkohenpdt <jkohen@pdtpartners.com>
* [bitnami/mongodb-sharded] Recover logging to stdout
The empty-dir volume mounted at /opt/bitnami/mongodb/logs (subPath
app-logs-dir) hides the mongodb.log -> /dev/stdout symlink created by the
container image at build time, so mongod writes a real file there instead of
logging to stdout.
Add a log-dir init container that recreates the symlink inside the volume,
mirroring the fix applied to the bitnami/mongodb chart in #27510, and wire it
into the config server, shard data, shard arbiter and mongos workloads.
Signed-off-by: shepherd.dev <shepherd9664@gmail.com>
* Trigger CI re-run
Signed-off-by: Gonzalo Gomez Gracia <gonzalo.gomez@broadcom.com>
ai-assisted=no
* Trigger CI re-run
Signed-off-by: Gonzalo Gomez Gracia <gonzalo.gomez@broadcom.com>
ai-assisted=no
---------
Signed-off-by: shepherd.dev <shepherd9664@gmail.com>
Signed-off-by: Gonzalo Gomez Gracia <gonzalo.gomez@broadcom.com>
Co-authored-by: Gonzalo Gomez Gracia <gonzalo.gomez@broadcom.com>
Add the marketing README for the distribution Helm chart, now available
in charts-private, following the pattern used for other Bitnami Secure
Images-only charts (e.g. openbao, reloader).
ai-assisted=yes
Ref: [TNZ-122380](https://vmw-jira.broadcom.net/browse/TNZ-122380)
Signed-off-by: Dan Goriaynov <dan.goriaynov@broadcom.com>
Add the marketing README for the future kong-operator Helm chart, mirroring the reloader chart's public README. This repo's README is a description-only stub (no Parameters section); the full chart implementation and its Parameters table will be added in the private charts-private repo as a separate, follow-up PR.
ai-assisted=yes
Ref: [TNZ-124370](https://vmw-jira.broadcom.net/browse/TNZ-124370)
Signed-off-by: Javier J. Salmerón García <javier.salmeron@broadcom.com>
Replaced the detailed README with a short marketing message indicating that the Helm chart is available under the Bitnami Secure Images initiative.
ai-assisted=yes
Ref: [TNZ-122381](https://vmw-jira.broadcom.net/browse/TNZ-122381)
Signed-off-by: Javier J. Salmerón García <javier.salmeron@broadcom.com>
* [bitnami/cortex] Add Cortex marketing README
ai-assisted=yes
Signed-off-by: Javier J. Salmerón García <javier.salmeron@broadcom.com>
* [bitnami/cortex] chore: 🔧 Update readme
ai-assisted=no
Signed-off-by: Javier J. Salmerón García <javier.salmeron@broadcom.com>
---------
Signed-off-by: Javier J. Salmerón García <javier.salmeron@broadcom.com>
Ensure helm.sh/chart and app.kubernetes.io/version labels still end with
an alphanumeric character after replacing + and truncating to
Kubernetes' 63-character label limit.
Resolves#36452
Signed-off-by: Peter Schiffer <3899107+pschiffe@users.noreply.github.com>
* support run prometheus server as statefulset
set server.workloadKind=StatefulSet to run as statefulset
Signed-off-by: Feng Shao <shaof777@gmail.com>
* change per review comment
change boolean flag useStatefulSet in values to controll deployment
type.
bump the chart to a new minor version since a new parameter is added.
Signed-off-by: Feng Shao <shaof777@gmail.com>
* update changelog
Signed-off-by: Feng Shao <shaof777@gmail.com>
* set update strategy and serviceName separately
Signed-off-by: Feng Shao <shaof777@gmail.com>
* fix: dynamically set apiVersion and kind for server deployment
Signed-off-by: Jota Martos <jota.martos@broadcom.com>
---------
Signed-off-by: Feng Shao <shaof777@gmail.com>
Signed-off-by: Jota Martos <jota.martos@broadcom.com>
Co-authored-by: Jota Martos <jota.martos@broadcom.com>
* [bitnami/thanos] per-shard extraFlags + shardLoopId in sharded storegateway
Brings the sharded storegateway in line with capabilities other sharded fields already provide:
- Each `timePartitioning` entry may now set its own `extraFlags` list, appended to the global `storegateway.extraFlags`. Mirrors the existing per-partition `resources` override.
- `topologySpreadConstraints` is now rendered with `shardLoopId` in context, matching what `affinity` / `nodeSelector` / `tolerations` already do. Users can write a per-shard label selector (e.g. `shard: '{{ .shardLoopId }}'`) so each shard's replicas spread independently.
Also defines `$partition` once at the top of the iteration loop rather than re-extracting it via `slice ... | first` in each block.
Signed-off-by: Elliot Kennedy <me@elken.io>
* Update CHANGELOG.md
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
---------
Signed-off-by: Elliot Kennedy <me@elken.io>
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
Co-authored-by: Bitnami Bot <bitnami.bot@broadcom.com>
