mammoth-afternoon-82670
09/30/2020, 6:56 PM--target
into the digitalocean.KubernetesCluster
, 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-16927
09/30/2020, 8:07 PMpulumi stack export --version=<previous-version-number> > out
followed by
pulumi stack import --file=out
mammoth-afternoon-82670
09/30/2020, 8:12 PMpulumi refresh --target urn:cluster
and it got the new kubeconfig, but as soon as I tried doing a pulumi refresh
it warns that the cluster is unreachable, and if by mistake I hit confirm, it deletes all the resources.kubeconfig
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 pulumi.log.error
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-16927
09/30/2020, 8:49 PMpulumi config set kubeconfig ...
)mammoth-afternoon-82670
09/30/2020, 9:25 PMgorgeous-egg-16927
09/30/2020, 9:41 PMmammoth-afternoon-82670
09/30/2020, 9:42 PMapply()
at least for the it's dependenciesgorgeous-egg-16927
09/30/2020, 9:56 PMmammoth-afternoon-82670
09/30/2020, 9:59 PM