This message was deleted.

sparse-intern-71089

10/13/2022, 9:18 AM

This message was deleted.

echoing-dinner-19531

10/13/2022, 9:52 AM

I would expect that telling
k8s.helm.v3.Chart
about the provider being the one I create it uses the kubeconfig from that provider

I would expect that to... but your kubeconfig line is commented out?

hundreds-yacht-71603

10/13/2022, 9:53 AM

Aha! Apparantly there's a massive difference between making the kubeconfig known and making the cluster known in the provider. Yeah, I mean if I tell it what the cluster is then I'd expect "the obvious" ... imho that means any k8s stuff that uses this provider uses the kubeconfig from that provider without being explicit about it

hundreds-yacht-71603

10/13/2022, 9:55 AM

Well, now it's back-off restarting container. Can I please have the monoliths back? They were working, at least 🙂

echoing-dinner-19531

10/13/2022, 10:00 AM

Yeh I'm not sure what setting just "cluster" would do, and I don't think I know k8s well enough to comment on if that would be the obvious answer or not. Feel free to open an issue about it on https://github.com/pulumi/pulumi-kubernetes/issues, the experts might have a comment to make.

48 Views

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.