-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for IngressClass introduced in Kubernetes v1.18 #357
Labels
Comments
9 tasks
Ran into this issue as well - apparently is not supported yet? |
Yes, this is still not supported. For now you can use the annotation if you need this: |
szuecs
pushed a commit
that referenced
this issue
Oct 22, 2021
…ing (#447) * #357 Implementation of spec.ingressClassName as a filter for ingress matching Signed-off-by: Tobias Günther <[email protected]> * Fix test, adopt test data to only use ingressClassName, add yet-another test case, that uses spec AND annotation ingress class. Signed-off-by: Tobias Günther <[email protected]> * replace pointer to string with empty string handling for json struct Signed-off-by: Tobias Günther <[email protected]> * rename checkFilterSupport to supportedIngressClass Signed-off-by: Tobias Günther <[email protected]> * add test for v1 ingress Signed-off-by: Tobias Günther <[email protected]>
Thanks to @Xyaren we have it now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Kubernetes v1.18 introduced a dedicated resource + field for defining
IngressClass
. See the documentation here: https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-classIt would make sense for the ingress-controller to support ingress class in this way going forward.
Related issue for skipper: zalando/skipper#1478
The text was updated successfully, but these errors were encountered: