On a related note the reason I am using a file is down to an

Question

On a related note the reason I am using a file is down to an issue using a multi line yaml string definition ```kubeconfig | apiVersion v1 clusters ``` This momentarily worked when I defined this way Then a few hours later pulumi cli started to error i e it worked w o issue but now it does not `error receiver must be a list or object not nili` `receiver must be a list or object not nil` `error an unhandled error occurred waiting for RPCs marshaling properties awaiting input property kubeconfig runtime error`

rich-agency-75207 · Answer

Has there been an update to the Pulumi backend over the last 24 hours Some properties of a kubernetes cluster resource were previously available It seems pulumi returns ` lt nil gt ` now for some of them including `masterAuth clusterCaCertificate` If so I would understand such a move considering the sensitivity of this data

rich-agency-75207 · Answer

Also for added context my inspiration to create a custom k8s provider and manual kubeconfig came from this Pulumi article <https www pulumi com blog kubernetes fundamentals part two >

rich-agency-75207 · Answer

Perhaps it is no longer relevant in context to Google s latest security standard and use of a cert

rich-agency-75207 · Answer

Please note when I tested ^ locally it works kube config is removed to ensure no authority exists that would facilitate a Pulumi gt GKE K8s API request kubectl tested as not work to confirm expected behaviour `pulumi up` does work I have tested creation of k8s objects via pulumi including updates and deletion

rich-agency-75207 · Answer

pulumi does not throw any errors on invocation and am using a custom provider that references `masterAuth clusterCaCertificate` via `kubeconfig `

rich-agency-75207 · Answer

However after some time pulumi does start to throw the error

rich-agency-75207 · Answer

Root cause is `masterAuth clusterCaCertificate` starts to return ` lt nil gt `

rich-agency-75207 · Answer

Is this expected behaviour

rich-agency-75207 · Answer

Having eyeballed the `masterAuth` property value via <http pulumi com|pulumi com> | Stack | resources I can also confirm that the `clusterCaCertificate` entry is still there and valid