Hello, I have one issue with

helm upgrade

1. already change the helm version and chart version (increment +1) 2. already change the rudder-server version

rudderlabs/rudder-server:1.9.3

3. when i ran

helm upgrade

; it show as completed -

Release "rudderstack" has been upgraded. Happy Helming!

4. but, when I edit the

rudderstack-0

pod, the value is not updated. and it keep show an error

ERROR	backend-config	Error sending request to the server: backend config request failed with 400: {"message":"Invalid workspace token"}

anyone know how to fix the helm upgrade?

Can you verify if you have a k8s secret in your namespace that is holding the workspace token.

Hi @narrow-rain-89253, thanks for your response . Yes it is. Issue resolved after I deleted existing pod. Do I need to delete before helm upgrade?

Should not be needed ideally but I am guessing the order of secret getting created and pod restarting after helm upgrade. We should probably look into adding annotation on secret to make it part of helm pre install hook