https://pulumi.com logo
#general
Title
# general
f

faint-motherboard-95438

12/12/2018, 2:21 PM
error: Plan apply failed: ingresses.extensions "[ingress name]" already exists
Would you guys have any idea why pulumi does not manage properly an update of an ingress on gcp ? it seems it wants to recreate it and fails while it knows that’s an update :
+-  └─ kubernetes:extensions:Ingress           [ingress name]             **replacing failed**     [diff: ~provider]; 1 error
Did I misconfigure something ? Everything else in my cluster is working and updating as expected