Closed alex1989hu closed 2 years ago
Hi, Thanks for spotting this out. Would you like to send a PR to fix it in redis ?
Hi, Thanks for spotting this out. Would you like to send a PR to fix it in redis ?
I have just sent 🎉
Hi, Thanks for your PR. Let's wait until it is reviewed and merged.
Hi, Thanks for your PR !!, it was merged.
Name and Version
bitnami/redis 16.5.4
What steps will reproduce the bug?
helm template redis ./redis/ -f redis-values.yaml > removeme.yaml
Are you using any custom parameters or values?
What is the expected behavior?
[]
{}
in Helm ChartsWhat do you see instead?
Additional information
"You can define one or multiple topologySpreadConstraint to instruct the kube-scheduler..." xref: https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/
Bitnami Helm Chart is mixing
[]
vs.{}
, I think the proper default value is:topologySpreadConstraints: []
Here we use
topologySpreadConstraints: []
:Here we use `topologySpreadConstraints: {}':