hey I constantly find myself having to nuke the ` garden` fo

Question

hey I constantly find myself having to nuke the ` garden` folder when switching between envs to avoid deploy failures is that something you do as well or am I taking placebo

brief-restaurant-63679 · Answer

Hmm I almost never find myself doing that What errors are you seeing when you don t

icy-furniture-17516 · Answer

this time it was trying to apply kubernetes resource from a kubernetes module the module installs a deployment but it seems garden tries to apply stuff on the pod ``` Command Users peterwilcsinszky garden tools kubectl f8a39834529cd1ed kubectl context= apply output=json f failed with code 1 Warning resource pods edge2 76f4d8567b kzbxm is missing the kubectl kubernetes io last applied configuration annotation which is required by kubectl apply kubectl apply should only be used on resources created declaratively by either kubectl create save config or kubectl apply The missing annotation will be patched automatically Error from server NotFound error when applying patch to Resource v1 Resource=pods GroupVersionKind v1 Kind=Pod Name edge2 76f4d8567b kzbxm Namespace for STDIN pods edge2 76f4d8567b kzbxm not found ```

icy-furniture-17516 · Answer

can that be because of the serviceResource setting ``` serviceResource podSelector app $ this name containerName dev ```

icy-furniture-17516 · Answer

seems to be completely unrelated to the garden folder

swift-garage-61180 · Answer

Hmm interesting Could you share the stack trace to help narrow this down I think it should be in `error log`

swift-garage-61180 · Answer

I m not sure why we d be calling `kubectl` on resources that are missing this annotation we specifically filter on only those resources but it s possible we re missing that filtering in some code path