This message was deleted.

I'm having an issue with the Kubernetes provider. We are passing an explicit kubeconfig into the provider, containing certificate information. However, the certificates will expire soon, so we need to replace them. However, changing the

kubeconfig

argument to the provider causes the provider to be replaced, which also causes all resources in the stack to be replaced! We've worked around this by doing some stack editing, and manually replacing the

kubeconfig

input in the stack state, so the change is not detected. This doesn't seem like a sustainable workflow though, what is the recommended way of rotating provider credentials?

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.