This message was deleted.
# general
s
This message was deleted.
o
I’ve created a function to generate a kubeconfig file from default credentials: https://gist.github.com/jelleklaver/7d040feecffdcf683b5d2dd646436533 It just doesn’t seem to work in our CI/CD pipeline yet..
b
I'm planning to try a similar pattern (on AWS) in coming weeks. Thanks for sharing your approach! I had planned to build a kubeconfig file dynamically as well, although this seems to be a pattern that is a bit off the beaten path (couldn't find many docs on the topic)
o
It is working now, however a major caveat of my current implementation is that this code runs before pulumi actually created the cluster at the cloud provider. So it won’t properly authenticate when the cluster gets created. It works only on subsequent runs (when the cluster gets updated) and if you have a predefined cluster name.
@billions-yak-67755 I’ve got it working with dynamic generation of the kubeconfig, using the Pulumi output api. Thought it might be of interest to you, so here’s the code: https://gist.github.com/jelleklaver/00468313a0a01b5a92cd5a91414952a6
b
That's awesome! Thanks so much for sharing! I am actually planning to get to do something similar tomorrow, so this will be super helpful!