i ve got a strange issue where pulumi keeps wanting to creat

Question

i ve got a strange issue where pulumi keeps wanting to create kubernetes resources that already exist but only if i run pulumi from a different machine with shared state files i assume it s a permissions issue of some sort but afaict pulumi s using the same ARM CLIENT ID etc on both machiens and I haven t got anywhere with fixing it any ideas please

microscopic-florist-22719 · Answer

< gorgeous egg 16927> any ideas

gorgeous-egg-16927 · Answer

My guess would be something to do with the kubeconfig you re using < better rainbow 14549> If you don t have the provider field specified for the k8s resources you re creating it defaults to using the ambient k8s creds context That can lead to weird results where it deploys some of the resources to an unintended cluster We re working to make that experience better in the near future

gorgeous-egg-16927 · Answer

<https github com pulumi examples blob ca1269141f085762ac5bc003da288270b35f11c2 azure ts aks mean index ts L34> is an example of the provider field I m talking about

better-rainbow-14549 · Answer

you were spot on about the providers i d missed it on one resource and when i ran it outside of CI they were going to a different cluster entirely

better-rainbow-14549 · Answer

i still have this problem though

better-rainbow-14549 · Answer

2018 12 14T10 32 17 4224963Z ++ kubernetes creating replacement diff ~provider 2018 12 14T10 32 17 4829687Z ++ kubernetes creating replacement diff ~provider 2018 12 14T10 32 17 5532715Z ++ kubernetes creating replacement diff ~provider error Plan apply failed already exists 2018 12 14T10 32 17 5535141Z ++ kubernetes creating failed diff ~provider error Plan apply failed already exists 2018 12 14T10 32 17 5850312Z ++ kubernetes creating replacement diff ~provider error Plan apply failed already exists 2018 12 14T10 32 17 5852450Z ++ kubernetes creating failed diff ~provider error Plan apply failed already exists 2018 12 14T10 32 17 6527655Z pulumi pulumi Stack goodfellow dev goodfellow dev 2018 12 14T10 32 17 6528561Z 2018 12 14T10 32 17 6528791Z Diagnostics 2018 12 14T10 32 17 6529188Z kubernetes 2018 12 14T10 32 17 6529473Z error Plan apply failed already exists 2018 12 14T10 32 17 6529676Z 2018 12 14T10 32 17 6529889Z kubernetes 2018 12 14T10 32 17 6530559Z error Plan apply failed already exists

better-rainbow-14549 · Answer

i just manually patched the provider in the state file nothing i tried would make it delete the CRD before updating them maybe that s simply not possible or could this be a bug

gorgeous-egg-16927 · Answer

< creamy potato 29402> ^ What s the expected behavior for CRDs

creamy-potato-29402 · Answer

What are you trying to do

creamy-potato-29402 · Answer

What does the plan look like

better-rainbow-14549 · Answer

I narrowed this issue to a couple of things i had a CRD where i hadn t specified the provider so it was using the one from my KUBECONFIG env var despite that not being a cluster i was using with pulumi the second was i was doing kubernetes Namespace getNamespace and that doesn t let you specify a provider at all it was doing the same

better-rainbow-14549 · Answer

fixed the first one but the second is still ongoing i can t see a way to get a reference to a namespace that already exists without it falling back to the env cluster

creamy-potato-29402 · Answer

< sparse insurance 40223> second issue shoudl be resolved in the last release

creamy-potato-29402 · Answer

First issue I will take back to the team and use as evidence that we should have better ambient provider support