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

Right now I embedded the kubeconfig and cluster list as secret values and loop through them.

Now I am facing that issue of possibly having only one at at time provided by a service connection in azure DevOps. Maybe it will create a kubeconfig. 
I was hoping to avoid a new stack for a new cluster that's supposed to be part of the same deployment essentially.

I might just have to push for the credentials to be accessible outside the service connection as a library variable group or something. Wanted to rule this out other options first since that will be more effort to get done.