It involves the use of a custom kubernetes provider and the

Question

It involves the use of a custom kubernetes provider and the Pulumi CLI failing after some undetermined time as the `cluster` | `masterAuth` | `clusterCaCertificate` value becomes opaque inaccessible to pulumi itself

rich-agency-75207 · Answer

```I0720 10 54 01 616272 7314 deployment executor go 260 deploymentExecutor Execute incoming event nil true Error an unhandled error occurred waiting for RPCs marshaling properties awaiting input property kubeconfig runtime error I0720 10 54 01 619147 7314 deployment executor go 304 deploymentExecutor Execute step executor has completed for worker threads to exit``` The root cause exists within the `kubeconfig` property of the custom provider resource It is the `certificate authority data` attribute referencing the GKE cluster `masterAuth clusterCaCertificate` property As previously mentioned this works fine for a while