ingressroutes are lost during scale up / scale down operations about k8ssandra HOT 9 CLOSED

@tomereli Applying --set in the command line resets the previous settings to defaults. From helm help:

--reuse-values when upgrading, reuse the last release's values and merge in any overrides from the command line via --set and -f. If '--reset-values' is specified, this is ignored

Thus, your previous setting of:

--set ingress.traefik.enabled=true

If set to false after you applied the --set size=3. To keep the previous ingress values, you need to apply the --reuse-values to your later upgrades. So, the size upgrade would be:

helm upgrade k8ssandra-cluster-a k8ssandra/k8ssandra-cluster --set size=3 --reuse-values

That is assuming the behavior is the same as before as described better in this article:

https://medium.com/@kcatstack/understand-helm-upgrade-flags-reset-values-reuse-values-6e58ac8f127e

from k8ssandra.

@jeffbanks I think you were in process of verifying this? Could you send update to the doc or should I?

@burmanm I will take care of updating the documentation to avoid future confusion. Thanks for the additional information here to assist @tomereli.

from k8ssandra.

@jeffbanks Can you take a look at this?

from k8ssandra.

Yes, researching and reaching out to get more information regarding commands in steps 5 & 6.

from k8ssandra.

Hi @tomereli can you provide some more details for us to further investigate?

What commands did you use for the following steps:

• Scale up the cluster to 3 nodes and wait for it to be fully operational
• Scale down the cluster back to 1 node

Also, did you possibly perform two Helm upgrade commands by chance? That could be wiping out the original settings.

from k8ssandra.

Hi @tomereli can you provide some more details for us to further investigate?

What commands did you use for the following steps:

• Scale up the cluster to 3 nodes and wait for it to be fully operational
• Scale down the cluster back to 1 node

Also, did you possibly perform two Helm upgrade commands by chance? That could be wiping out the original settings.

I used helm upgrade commands to scale up and down, according to the documentation:
scale up - https://k8ssandra.io/docs/topics/provision-a-cluster/#scale-up-the-cluster
scale down - https://k8ssandra.io/docs/topics/provision-a-cluster/#scale-down-the-cluster

What do you mean that it could be wiping out the original settings?

from k8ssandra.

Thanks for providing the details. I wanted to verify that those steps didn't override something previously set. I was referring to how multiple helm upgrades or two same key assignments can override the original intention.
helm upgrade --set foo=bar --set foo=baz k8ssandra ./k8ssandra

Helm upgrade reference

Given this detail, I will go through your exact steps and attempt to reproduce this locally.

from k8ssandra.

@tomereli Applying --set in the command line resets the previous settings to defaults. From helm help:

--reuse-values when upgrading, reuse the last release's values and merge in any overrides from the command line via --set and -f. If '--reset-values' is specified, this is ignored

Thus, your previous setting of:

--set ingress.traefik.enabled=true

If set to false after you applied the --set size=3. To keep the previous ingress values, you need to apply the --reuse-values to your later upgrades. So, the size upgrade would be:

helm upgrade k8ssandra-cluster-a k8ssandra/k8ssandra-cluster --set size=3 --reuse-values

That is assuming the behavior is the same as before as described better in this article:

https://medium.com/@kcatstack/understand-helm-upgrade-flags-reset-values-reuse-values-6e58ac8f127e

Well I guess this is it then - nice catch. I think it would be good to add this to the documentation, cause I guess more users may fall in this pitfall.

from k8ssandra.

@jeffbanks I think you were in process of verifying this? Could you send update to the doc or should I?

from k8ssandra.