https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
r
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 
<nil>
now for some of them including 
masterAuth.clusterCaCertificate
If so, I would understand such a move considering the sensitivity of this data.
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/
Perhaps it is no longer relevant in context to Google's latest security standard and use of a cert..?
Please note - when I tested ^ locally - it works. ./kube/config is removed to ensure no authority exists that would facilitate a Pulumi --> 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.
pulumi does not throw any errors on invocation and am using a custom-provider that references 
masterAuth.clusterCaCertificate
via 
kubeconfig:
However, after some time, pulumi does start to throw the error.
Root cause is 
masterAuth.clusterCaCertificate
starts to return 
<nil>
Is this expected behaviour?
Having eyeballed the 
masterAuth
property value, via pulumi.com | Stack | resources - I can also confirm that the 
clusterCaCertificate
entry is still there and valid.
7 Views
Open in Slack
PreviousNext
Powered by

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.

Powered by