You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of 2.1, KIC treats ingressClassName identically to the deprecated class annotation: if the listed class matches the controller's configured class, it ingests the Ingress.
Ingress v1 should actually interact with IngressClass resources in some fashion.
Closing this as we already have a separate issue for the remaining functionality without plans to start work on it immediately. #2292 and #2313 cover the functionality that wasn't tracked elsewhere.
Is there an existing issue for this?
Problem Statement
As of 2.1, KIC treats ingressClassName identically to the deprecated class annotation: if the listed class matches the controller's configured class, it ingests the Ingress.
Ingress v1 should actually interact with IngressClass resources in some fashion.
Proposed Solution
Implement Service-upstream default controlled by IngressClass parameters #1131Additional information
No response
Acceptance Criteria
Service-upstream default controlled by IngressClass parameters #1131 is doneto be handled in that issue.The text was updated successfully, but these errors were encountered: