No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

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?