This message was deleted.

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.