If the annotation is not set, Contour will ignore the Ingress.If you do this, the behavior is as follows: This can be useful while you are migrating from another controller, or if you need multiple instances of Contour. You can override the default class contour by providing the -ingress-class-name flag to Contour. If any other value, Contour ignores the Ingress definition.If specified as kubernetes.io/ingress.class: contour, then Contour serves the Ingress.If not set, then all Ingress controllers serve the Ingress.In both cases, they will behave as follows, by default: This annotation may be specified as the standard kubernetes.io/ingress.class or a Contour-specific projectcontour.io/ingress.class. The Ingress class annotation can be used to specify which Ingress controller should serve a particular Ingress object. The following Kubernetes annotations are supported on Ingress objects: Ingress Class However, Contour still supports a number of annotations on the Ingress resources. HTTPProxy API, which provides a more robust configuration interface over Some of the features that have been historically configured via annotations are supported as first-class features in Contour’s
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |