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

```pulumi stack output kubeconfig --show-secrets &gt; kubeconfig.yaml
KUBECONFIG=./kubeconfig.yaml kubectl get nodes```

If I remember correctly we use az cli to login with sp and the new kubelogin plugin to get kubectl access. If we run this before pulumi, pulumi can use the default kubecontext on the machine. It is a chicken and egg problem, since you can't login unless the cluster is created.

You might be able to run the az login steps from the pulumi script to be sure that the cluster is up