IngressClass support in CRDs

[de1chk1nd]

Title

IngressClass support in CRDs

Description

Support of IngressClass Feature in CRDs.

Actual Problem

Currently CIS in CRD mode only has limited support for multiple Ingress Controller (e.g. having two separate BigIPs which need to send traffic into the k8s cluster).
Today's solution is based on namespaces (CIS CTRL to monitor certain namespaces), which is not as flexible, as supporting IngressClass feature.

Solution Proposed

Support IngressClass in CRDs

Alternatives

See above statement - CIS CTRL tied to a namespace is/was tested but not flexible enough.

Additional context

Similar issue can be found here: #3559

[trinaths]

reg,

CIS CTRL tied to a namespace is/was tested but not flexible enough.

Please give more info about NS flexibility with BIG-IP. Send the info to automation_toolchain_pm at f5 dot com

[skenderidis]

I have seen the same request from at least 3-5 other customers. Adding and removing additional NS on the CIS CTRL (where the backend services are running), is not something customers want to do because it requires restart of the CIS CTRL