mammoth-afternoon-8267009/30/2020, 6:56 PM
, which brought a new kubeconfig content, but for some reason it doesn't seem to be used by the provider at all. Still getting
configured Kubernetes cluster is unreachable: unable to load schema information from the API server: the server has asked for the client to provide credentials
gorgeous-egg-1692709/30/2020, 8:07 PM
pulumi stack export --version=<previous-version-number> > out
pulumi stack import --file=out
mammoth-afternoon-8267009/30/2020, 8:12 PM
and it got the new kubeconfig, but as soon as I tried doing a
pulumi refresh --target urn:cluster
it warns that the cluster is unreachable, and if by mistake I hit confirm, it deletes all the resources.
updated when using DigitalOcean clusters: https://github.com/pulumi/examples/blob/master/digitalocean-ts-k8s/index.ts#L29-L36 But for some reason this is not working at all. It doesn't seem to catch the updated kubeconfig, and putting a
in the apply callback doesn't seem to fire to. I'm assuming this is never getting called after the first provisioning? Really confused right now and unable to properly debug it.
gorgeous-egg-1692709/30/2020, 8:49 PM
pulumi config set kubeconfig ...
mammoth-afternoon-8267009/30/2020, 9:25 PM
gorgeous-egg-1692709/30/2020, 9:41 PM
mammoth-afternoon-8267009/30/2020, 9:42 PM
at least for the it's dependencies
gorgeous-egg-1692709/30/2020, 9:56 PM
mammoth-afternoon-8267009/30/2020, 9:59 PM