Ingress not generating hostnames

Rancher 2.x
1

Hi,

I had everything working correctly but now it seems that ingress is no longer able to generate any hostnames. I have 3 previous ingress that are still working fine but I unable to create any new ones. I am getting the following errors in the nginx-ingress-controller logs that may be related but I have no idea what is referencing these services:

W0420 09:51:09.480448 6 controller.go:694] Error obtaining Endpoints for Service "default/ingress-66e93587d04531d448a5fffba43148f9": error getting Service "default/ingress-66e93587d04531d448a5fffba43148f9" from local store: service default/ingress-66e93587d04531d448a5fffba43148f9 was not found

20/04/2019 10:51:09 W0420 09:51:09.480477 6 controller.go:694] Error obtaining Endpoints for Service “default/ingress-4ab28d6786d94fd38f49cca902401130”: error getting Service “default/ingress-4ab28d6786d94fd38f49cca902401130” from local store: service default/ingress-4ab28d6786d94fd38f49cca902401130 was not found

20/04/2019 10:51:09 W0420 09:51:09.480496 6 controller.go:694] Error obtaining Endpoints for Service “default/ingress-2937022441fcce078500a6cc80d03b25”: error getting Service “default/ingress-2937022441fcce078500a6cc80d03b25” from local store: service default/ingress-2937022441fcce078500a6cc80d03b25 was not found

I am unsure where else to check for issues as it appears that everything else is working correctly and as I say this was working fine until a couple of days ago.

1 Like
2

As a followup, I am seeing the below when trying to view/edit yaml for ingresses:

image
image1478Ă—250 7.95 KB

3

I’m seeing the exact same thing. I wasn’t having this issue with build 2.2.1, however when deploying build 2.2.2 (from scratch) I can no longer deploy any new ingress points. This makes it impossible to use the platform as both the stable and latest builds are both using 2.2.2.