Describe the bug
When defining sidecar containers in the helm yaml for any mongodb pod (configsrv, mongos, shardsvr.arbiter or shardsvr.dataNode) that definitions are ignored. No additional containers appear in the output yaml nor are any containers created in kubernetes.
You see bitnami/node right after sidecars: two times - each time it is just the definition of the myValues.yaml.
But there is no image 'bitnami/node' added in the containers section of any output *-statefulset.yaml.
If I do not do a dry run, but a real deploy, when I do
kubectl get pods -n my-test-space
NAME READY STATUS RESTARTS AGE
my-test-mongodb-sharded-configsvr-0 1/1 Running 1 3m10s
my-test-mongodb-sharded-mongos-547dcdccf5-k46xk 1/1 Running 0 3m10s
my-test-mongodb-sharded-shard0-data-0 1/1 Running 3 3m10s
my-test-mongodb-sharded-shard1-data-0 1/1 Running 3 3m10s
Expected behavior
When defining a sidecar like above, there should be an additional entry in the containers section of
# Source: mongodb-sharded/templates/config-server/config-server-statefulset.yaml
..
spec:
selector:
matchLabels:
app.kubernetes.io/name: mongodb-sharded
app.kubernetes.io/instance: my-test
app.kubernetes.io/component: configsvr
..
template:
..
spec:
..
containers:
- name: mongodb
..
- name: mytest
image: bitnami/node
imagePullPolicy: IfNotPresent
Additionally I would expect certain mongo settings like the root password also be available in those sidecars:
env:
- name: MONGODB_ROOT_PASSWORD
valueFrom:
secretKeyRef:
name: my-test-mongodb-sharded
key: mongodb-root-password
If I do not do a dry run, but a real deploy, when I do
kubectl get pods -n my-test-space
I exprect to see:
NAME READY STATUS RESTARTS AGE
my-test-mongodb-sharded-configsvr-0 2/2 Running 1 3m10s
my-test-mongodb-sharded-mongos-547dcdccf5-k46xk 1/1 Running 0 3m10s
my-test-mongodb-sharded-shard0-data-0 1/1 Running 3 3m10s
my-test-mongodb-sharded-shard1-data-0 1/1 Running 3 3m10s
There is an additional container running. - configsvr-0 2/2
Which chart: bitnami/mongodb-sharded
Describe the bug When defining sidecar containers in the helm yaml for any mongodb pod (configsrv, mongos, shardsvr.arbiter or shardsvr.dataNode) that definitions are ignored. No additional containers appear in the output yaml nor are any containers created in kubernetes.
To Reproduce Steps to reproduce the behavior:
You see bitnami/node right after sidecars: two times - each time it is just the definition of the myValues.yaml. But there is no image 'bitnami/node' added in the containers section of any output *-statefulset.yaml. If I do not do a dry run, but a real deploy, when I do kubectl get pods -n my-test-space
Expected behavior When defining a sidecar like above, there should be an additional entry in the containers section of
If I do not do a dry run, but a real deploy, when I do kubectl get pods -n my-test-space I exprect to see:
There is an additional container running. - configsvr-0 2/2
Version of Helm and Kubernetes:
helm version
:kubectl version
:Additional context N/A