Better Logs for wrong ingress class

[alex-bezek]

Description

While setting up some demos, I ran into an issue where my ingress wasn't being created and I was missing why. Eventually I did find this

2023-03-13T22:27:51Z INFO controllers.ingress Ingress is not of type ngrok so skipping it {"ingress": "default/game-2048"}

My issue was I had the ingress-class annotation instead of the spec attribute. This would have been more clear if:

• we noticed that annotation and warned that it was deprecated and being ignored
• if the error said what the ingress class of the ingress was
• if the error also said what the ingress classes it knows about and which that particular controller is watching.

Use Case

It should be easy to deal with misconfigurations.

Related issues

No response