Is it possible to have pulumi default to “my current cluster”, when running the automation api inside a k8s pod?
Context: I’m building a service that will be able to deploy some k8s resources using Pulumi. The service itself runs inside a k8s pod. I don’t want to hard-code the kubeconfig for my service. Rather, I just want it to create the resources in whatever cluster it’s running, so that I can run it in different clusters without having to change the code/configuration. Is this possible? thanks!
11/16/2020, 8:36 PM
the pod you're running the cluster in should provide default service account, which you can then use to authenticate