Specific Errors and Warnings for Unsupported Ingress Configurations

[alex-bezek]

Description

There are some portions of the ingress spec which we do not support. Because of how ingress objects merge to form edges, there are also combinations of ingress objects that cause conflicts.

In the driver's sync function, we should collect any of these issues and emit logs and events signaling to the user the issue. These include the following:

• Default backends are not supported and will be dropped transparently
• Rules without hostnames are not supported and will be dropped transparently
• If 2 ingress objects have the same rule host and path, they will conflict. The one processed first will be dropped.

Use Case

While there will be other types of errors and misconfigurations, this covers the known "surprising" issues that are in the ingress spec but not supported, or have implementation-specific details.

Related issues

No response

[alex-bezek]

It might also be worth ordering all the ingress objects by timestamp as noted in

https://kubernetes.github.io/ingress-nginx/how-it-works/#building-the-nginx-model

Order Ingress rules by CreationTimestamp field, i.e., old rules first.