mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-07-23 19:56:01 +00:00
first shot improving api doc for ingressclassname
This commit is contained in:
parent
92a1d0f84c
commit
e1ce5a682b
@ -302,16 +302,16 @@ type IngressList struct {
|
||||
|
||||
// IngressSpec describes the Ingress the user wishes to exist.
|
||||
type IngressSpec struct {
|
||||
// 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.
|
||||
// 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 bound 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 the annotation should still be honored if present.
|
||||
// +optional
|
||||
IngressClassName *string `json:"ingressClassName,omitempty" protobuf:"bytes,4,opt,name=ingressClassName"`
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user