Question

<https github com helm charts tree master stable prometheus operator kubeproxy> Is there an easy way to do the above with Pulumi

worried-city-86458 · Answer

Is the only option to shell out to kubectl

worried-city-86458 · Answer

< white balloon 205> apologies for the mention but the above is another common pattern I m seeing and hoping for some direction ideas

worried-city-86458 · Answer

Is there a nice way to do read modify write patching of existing k8s resources with pulumi

worried-city-86458 · Answer

If it means shelling out then even that could do with some help from pulumi making kubectl more first class

white-balloon-205 · Answer

It would be good to open an issue in pulumi kubernetes with details of the use cases here We did add a `kubectlReplace` function to the Kubernetes provider related to this but I m not sure it really completely solves for common scenarios and would love to have an issue tracking these to make sure we think about what a great solution here would look like <https github com pulumi pulumi kubernetes pull 579>

clever-nest-47198 · Answer

This is killing us a bit We ve written our own Python eks pulumi library that stands up the control plane worker nodes and we re flying with it however we have a massive hole in our upgrade story as we re unable to nicely upgrade kube proxy coredns aws vpc cni

white-balloon-205 · Answer

You can see how this is handled in the ` pulumi eks` package for Node js here <https github com pulumi pulumi eks blob master nodejs eks cni ts L160>

white-balloon-205 · Answer

You should be able to do the same from a Python package

clever-nest-47198 · Answer

Very intimately familiar we ve written our own dynamic provider code using a python kubernetes lib instead of shelling out just unfortunate that it has to be done that way

white-balloon-205 · Answer

FWIW this is an issue tracking this definitely feel free to add a note about your scenario and an upvote <https github com pulumi pulumi kubernetes issues 264>