busy-soccer-65968
03/31/2021, 4:47 PMapiVersion
on an ingress is different than what it actually is. Basically in reality my ingress is extensions/v1beta1
but when I refresh pulumi changes state to <http://networking.k8s.io/v1|networking.k8s.io/v1>
and then when I preview it shows it wanting to change it to extensions/v1beta1
which it already is... I'm also seeing this 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
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.serviceName
to service.name
in the newer api.No matching service found for ingress rule: "<http://topsecret.stage.myrootdomain.net|topsecret.stage.myrootdomain.net>" -> ""
which leads me to believe it's getting undefined trying to access the incorrect property.apiVersion: extensions/v1beta1
so I really have no idea where pulumi is deciding oh wait a second this is the new api` No matching service found for ingress rule:
but it's not true. the service is found and the ingress even worksfuture-refrigerator-88869
03/31/2021, 8:21 PMnew k8s.networking.v1.Ingress(...)
busy-soccer-65968
03/31/2021, 8:23 PMcheckIfEndpointsReady
Even tried SkipAwait:true annotation and it didn't help```