10/13/2022, 10:22 PM
Hi everyone! Quick question that I can't seem to find anything about online, but thought that it'd be a common usecase: I use pulumi to provision deployments in my setup, but after that I want to manage number of replicas and container images outside of pulumi (we have pipelines doing that already). I know
help to some extent, but whenever we need to change a deployment configuration it will reset the number of replicas and/or the image there. So my question is: is there a way of defining a specific field of a kubernetes resource to not be managed by pulumi? If not, what is the "normal" way of using pulumi with kubernetes deployments?
Worth noting that I did experiment with server-side apply, but it doesn't seem to cut it - it needs
flag to change stuff such as resource limits apparently
I'm also trying to follow this example but couldn't find a way of skipping validation