From c71c4e7cdbeff8e82453912c92bae6a09768d4ae Mon Sep 17 00:00:00 2001 From: Daneyon Hansen Date: Thu, 11 Feb 2021 10:55:49 -0800 Subject: [PATCH] Fixes Typo in HTTPRoute Godocs --- apis/v1alpha1/httproute_types.go | 2 +- config/crd/bases/networking.x-k8s.io_httproutes.yaml | 2 +- docs-src/spec.md | 4 ++-- docs/spec/index.html | 4 ++-- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/apis/v1alpha1/httproute_types.go b/apis/v1alpha1/httproute_types.go index 83160cf906..3d7cf86c67 100644 --- a/apis/v1alpha1/httproute_types.go +++ b/apis/v1alpha1/httproute_types.go @@ -92,7 +92,7 @@ type HTTPRouteSpec struct { // // Collisions can happen if multiple HTTPRoutes define a TLS certificate // for the same hostname. In such a case, conflict resolution guiding - // principles apply, specificallly, if hostnames are same and two different + // principles apply, specifically, if hostnames are same and two different // certificates are specified then the certificate in the // oldest resource wins. // diff --git a/config/crd/bases/networking.x-k8s.io_httproutes.yaml b/config/crd/bases/networking.x-k8s.io_httproutes.yaml index 1964c94d32..d0cae8ffeb 100644 --- a/config/crd/bases/networking.x-k8s.io_httproutes.yaml +++ b/config/crd/bases/networking.x-k8s.io_httproutes.yaml @@ -411,7 +411,7 @@ spec: maxItems: 16 type: array tls: - description: "TLS defines the TLS certificate to use for Hostnames defined in this Route. This configuration only takes effect if the AllowRouteOverride field is set to true in the associated Gateway resource. \n Collisions can happen if multiple HTTPRoutes define a TLS certificate for the same hostname. In such a case, conflict resolution guiding principles apply, specificallly, if hostnames are same and two different certificates are specified then the certificate in the oldest resource wins. \n Please note that HTTP Route-selection takes place after the TLS Handshake (ClientHello). Due to this, TLS certificate defined here will take precedence even if the request has the potential to match multiple routes (in case multiple HTTPRoutes share the same hostname). \n Support: Core" + description: "TLS defines the TLS certificate to use for Hostnames defined in this Route. This configuration only takes effect if the AllowRouteOverride field is set to true in the associated Gateway resource. \n Collisions can happen if multiple HTTPRoutes define a TLS certificate for the same hostname. In such a case, conflict resolution guiding principles apply, specifically, if hostnames are same and two different certificates are specified then the certificate in the oldest resource wins. \n Please note that HTTP Route-selection takes place after the TLS Handshake (ClientHello). Due to this, TLS certificate defined here will take precedence even if the request has the potential to match multiple routes (in case multiple HTTPRoutes share the same hostname). \n Support: Core" properties: certificateRef: description: "CertificateRef refers to a Kubernetes object that contains a TLS certificate and private key. This certificate MUST be used for TLS handshakes for the domain this RouteTLSConfig is associated with. If an entry in this list omits or specifies the empty string for both the group and kind, the resource defaults to \"secrets\". An implementation may support other resources (for example, resource \"mycertificates\" in group \"networking.acme.io\"). \n Support: Core (Kubernetes Secrets) Support: Implementation-specific (Other resource types)" diff --git a/docs-src/spec.md b/docs-src/spec.md index 03fb362791..a8c7740c65 100644 --- a/docs-src/spec.md +++ b/docs-src/spec.md @@ -541,7 +541,7 @@ Route. This configuration only takes effect if the AllowRouteOverride field is set to true in the associated Gateway resource.

Collisions can happen if multiple HTTPRoutes define a TLS certificate for the same hostname. In such a case, conflict resolution guiding -principles apply, specificallly, if hostnames are same and two different +principles apply, specifically, if hostnames are same and two different certificates are specified then the certificate in the oldest resource wins.

Please note that HTTP Route-selection takes place after the @@ -2617,7 +2617,7 @@ Route. This configuration only takes effect if the AllowRouteOverride field is set to true in the associated Gateway resource.

Collisions can happen if multiple HTTPRoutes define a TLS certificate for the same hostname. In such a case, conflict resolution guiding -principles apply, specificallly, if hostnames are same and two different +principles apply, specifically, if hostnames are same and two different certificates are specified then the certificate in the oldest resource wins.

Please note that HTTP Route-selection takes place after the diff --git a/docs/spec/index.html b/docs/spec/index.html index 6921121d74..c393c03b06 100644 --- a/docs/spec/index.html +++ b/docs/spec/index.html @@ -1108,7 +1108,7 @@

HTTPRoute field is set to true in the associated Gateway resource.

Collisions can happen if multiple HTTPRoutes define a TLS certificate for the same hostname. In such a case, conflict resolution guiding -principles apply, specificallly, if hostnames are same and two different +principles apply, specifically, if hostnames are same and two different certificates are specified then the certificate in the oldest resource wins.

Please note that HTTP Route-selection takes place after the @@ -3184,7 +3184,7 @@

HTTPRouteSpec field is set to true in the associated Gateway resource.

Collisions can happen if multiple HTTPRoutes define a TLS certificate for the same hostname. In such a case, conflict resolution guiding -principles apply, specificallly, if hostnames are same and two different +principles apply, specifically, if hostnames are same and two different certificates are specified then the certificate in the oldest resource wins.

Please note that HTTP Route-selection takes place after the