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
IngressClassName is the name of the IngressClass cluster resource. The associated IngressClass defines which controller will implement the resource. This replaces the deprecated `kubernetes.io/ingress.class` annotation. For backwards compatibility, when that annotation is set, it must be given precedence over this field. The controller may emit a warning if the field and annotation have different values. Implementations of this API should ignore Ingresses without a class specified. An IngressClass resource may be marked as default, which can be used to set a default value for this field. For more information, refer to the IngressClass documentation.
91
+
IngressClassName is the name of an IngressClass cluster resource. Ingress controller implementations use this field to know whether they should be serving this Ingress resource, by a transitive connection (controller -> IngressClass -> Ingress resource). Although the `kubernetes.io/ingress.class` annotation (simple constant name) was never formally defined, it was widely supported by Ingress controllers to create a direct binding between Ingress controller and Ingress resources. Newly created Ingress resources should prefer using the field. However, even though the annotation is officially deprecated, for backwards compatibility reasons, ingress controllers should still honor that annotation if present.
Host is the fully qualified domain name of a network host, as defined by RFC 3986. Note the following deviations from the "host" part of the URI as defined in RFC 3986: 1. IPs are not allowed. Currently an IngressRuleValue can only apply to
125
125
the IP in the Spec of the parent Ingress.
126
126
2. The `:` delimiter is not respected because ports are not allowed.
127
-
Currently the port of an Ingress is implicitly :80 for http and
128
-
:443 for https.
127
+
Currently the port of an Ingress is implicitly :80 for http and
128
+
:443 for https.
129
129
Both these may change in the future. Incoming requests are matched against the host before the IngressRuleValue. If the host is unspecified, the Ingress routes all traffic based on the specified IngressRuleValue.
PathType determines the interpretation of the Path matching. PathType can be one of the following values: * Exact: Matches the URL path exactly. * Prefix: Matches based on a URL path prefix split by '/'. Matching is
207
+
PathType determines the interpretation of the Path matching. PathType can be one of the following values:
208
+
209
+
* Exact: Matches the URL path exactly.
210
+
211
+
* Prefix: Matches based on a URL path prefix split by '/'. Matching is
208
212
done on a path element by element basis. A path element refers is the
209
213
list of labels in the path split by the '/' separator. A request is a
210
214
match for path p if every p is an element-wise prefix of p of the
0 commit comments