"Ignore update for invalid class" misleading log

[paovitali]

Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.): No

What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.): ingress.class, ignoring updates

NGINX Ingress controller version: 0.22

Kubernetes version (use kubectl version): 1.10.5

Environment: Bare Metal

• Cloud provider or hardware configuration: Bare Metal
• OS (e.g. from /etc/os-release): Ubuntu 16.04.3 LTS
• Kernel (e.g. uname -a): 4.4.0-109-generic
• Install tools: Puppet

What happened: Starting from 0.22 release, in raw-app logs I see at every reload/nginx change an INFO log line stating store.go:393] ignoring ingress <ingress-app> based on annotation kubernetes.io/ingress.class for each NS.

This line appears even if NO "ingress.class" annotations are set in any of k8s ingress objects and NO "ingress-class" controller argument deployment flag is set, condition that should be considered as "valid" in the check for annotations.

What you expected to happen: When the "ingress.class" annotation is not used this log line should not appear or it should have a dedicated different message like No changes on ingress for < NS > - skipping update. Also it would be a nice to have to make this log configurable (if not already possible)

How to reproduce it (as minimally and precisely as possible): Just fire up a 0.22 release in a cluster with no "ingress.class" settings in both rules/controller.

Anything else we need to know: This is the PR that included that new log line #3532