Here I am. So, yes, the ideal flow would be to sav...
# umh-support
d
Here I am. So, yes, the ideal flow would be to save the values that the user changed and use them to overwrite the values of the new chart version each time. This way, like you said, all the new defaults get applied, along with the user's custom modifications. Tbf, this is a more "technincal" solution, and for the average user might be more difficult to follow As far as your specific error, my assumption is that you changes your values, and specifically the
redpanda.statefulset.topologySpreadConstraints
field. In the default values provided by us, we do not change it. So you should take a look at what value you are setting there and adjust them. The error is saying that you are using an object instead of an array. This means that your values looks something like this
Copy code
yaml
redpanda:
  statefulset:
    topologySpreadConstraints:
      maxSkew: 1
      topologyKey: topology.kubernetes.io/zone
      whenUnsatisfiable: ScheduleAnyway
Instead of like this (notice the
-
sign):
Copy code
yaml
redpanda:
  statefulset:
    topologySpreadConstraints:
    - maxSkew: 1
      topologyKey: topology.kubernetes.io/zone
      whenUnsatisfiable: ScheduleAnyway
You can use the
helm get values united-manufacturing-hub
command to get the user-submitted values, and add the
-a
flag to that command to get all the computed values
2 Views