![]() ![]() Defaults to Envoy’s default behavior which is use_websocket to false. The routes supporting websocket protocol, the annotation value contains a list of route paths separated by a comma that must match with the ones defined in the Ingress definition. ![]() The minimum TLS protocol version the TLS listener should support. projectcontour.io/tls-minimum-protocol-version:.Possible values and their meanings for retry-on. The conditions for Envoy to retry a request. Note that the value 0s / zero has special semantics for Envoy. Set this to infinity to specify that Envoy should never timeout the connection to the backend. By default, Envoy has a 15 second timeout for a backend service to respond. The Envoy HTTP route timeout, specified as a Applies only if projectcontour.io/retry-on is specified. The timeout per retry attempt, if there should be one. The maximum number of retries Envoy should make before abandoning and returning an error to the client. Main Ingress class annotation section for more details. projectcontour.io/ingress.class: The Ingress class that should interpret and serve the Ingress.If they are set to "true" and "false" respectively, Contour will create an Envoy HTTP route for the Virtual host, and set the require_tls virtual host option. The /force-ssl-redirect annotation takes precedence over kubernetes.io/ingress.allow-http. Specify "false" for Envoy to mark the endpoint as HTTPS only. The Ingress exists only for HTTPS requests. kubernetes.io/ingress.allow-http: Instructs Contour to not create an Envoy HTTP route for the virtual host./force-ssl-redirect: Requires TLS/SSL for the Ingress to Envoy by setting the.Contour will serve the Ingress or HTTPProxy if the annotation or IngressClassName matches any of the specified class name values. _Note: The -ingress-class-name value can be a comma-separated list of class names to match against. If both the annotation and the spec field are specified on an object, the annotation takes preference for backwards compatibility. Going forward this is the preferred way to specify an ingress class, rather than using an annotation. Note: Both Ingress and HTTPProxy now have an IngressClassName field in their spec. This same logic applies for these annotations on HTTPProxy objects. If the annotation matches the value that you passed to -ingress-class-name flag, Contour will serve the Ingress.If the annotation is set to any value other than the one passed to the -ingress-class-name flag, Contour will ignore the Ingress.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 annotations. Some of the features that have been historically configured via annotations are supported as first-class features in Contour’s How to Configure PROXY Protocol v1/v2 SupportĪnnotations are used in Ingress Controllers to configure features that are not covered by the Kubernetes Ingress API.Creating a Contour-compatible kind cluster.Configuring ingress to gRPC services with Contour.Deploying HTTPS services with Contour and cert-manager.AWS Network Load Balancer TLS Termination with Contour.
0 Comments
Leave a Reply. |