This message was deleted.

@broad-dog-22463 thoughts here?

I'm thinking that I'll need to use doctl to generate a fresh kubeconfig each time my app deploy pipelines run, pass the path to it into my pulumi update command as an env var, and load the file as the provider rather than depending upon the one exported in the main cluster stack.

Would it be better if we gave a way to get KubeConfig from the code and then it would refresh each time the certificate changes in a refresh?

That sounds good to me.