busy-soccer-6596803/31/2021, 4:47 PM
on an ingress is different than what it actually is. Basically in reality my ingress is
but when I refresh pulumi changes state to
and then when I preview it shows it wanting to change it to
which it already is... I'm also seeing this
which is also around this helmchart and ingress. I found an issue form 2020 around this. Basically then it was simply a misconfigured helmchart. However, I have confirmed that my labels are correct and my label selectors all line up.
Ingress has at least one rule that does not target any Service. Field '.spec.rules.http.paths.backend.serviceName' may not match any active Service
in the newer api.
which leads me to believe it's getting undefined trying to access the incorrect property.
No matching service found for ingress rule: "<http://topsecret.stage.myrootdomain.net|topsecret.stage.myrootdomain.net>" -> ""
so I really have no idea where pulumi is deciding oh wait a second this is the new api
but it's not true. the service is found and the ingress even works
` No matching service found for ingress rule:
future-refrigerator-8886903/31/2021, 8:21 PM
busy-soccer-6596803/31/2021, 8:23 PM
Even tried SkipAwait:true annotation and it didn't help```