This message was deleted.

sparse-intern-71089

02/06/2023, 1:08 PM

This message was deleted.

salmon-account-74572

02/06/2023, 4:38 PM

You have to use a function to pull the credentials, and then build a Kubeconfig from those credentials. Have a look at one of the

kubernetes-azure-*

templates in the Pulumi templates repository (https://github.com/pulumi/templates) for an example of how to do that.

salmon-account-74572

02/06/2023, 4:39 PM

Once you have the Kubeconfig, then you can build a Kubernetes provider that uses it, or pass it to

kubectl

for CLI access.

salmon-account-74572

02/06/2023, 4:41 PM

One additional note: by default, the Kubeconfig created by AKS uses a

devicelogin

configuration and won’t leverage the Azure CLI authentication. See this blog post to switch it (which makes it a tad easier IMO): https://blog.scottlowe.org/2022/10/06/streamlining-the-user-experience-for-accessing-aks-clusters/

polite-summer-58169

02/07/2023, 8:40 AM

Thanks Scott! We're currently connecting using the Command package that's in preview. And then calling

az aks get-credentials

through that. But that throws an error so maybe not the way to do it...

polite-summer-58169

02/07/2023, 8:40 AM

Thanks a lot for pointing at the templates. I wish we would've seen those a long time ago 🙂

salmon-account-74572

02/07/2023, 2:30 PM

You should be able to “steal” code from the templates to add to your own projects in order to generate a Kubeconfig. Let us know if you need some help in that direction.

Open in Slack

Previous Next

Pulumi Community

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.