routes/ingress: run make update

openshift-cherrypick-robot · Aug 11, 2020 · ff58754 · ff58754
1 parent b0b353e
commit ff58754
Show file tree

Hide file tree

Showing 3 changed files with 9 additions and 5 deletions.
diff --git a/operator/v1/0000_50_ingress-operator_00-ingresscontroller.crd.yaml b/operator/v1/0000_50_ingress-operator_00-ingresscontroller.crd.yaml
@@ -54,9 +54,13 @@ spec:
                 a wildcard certificate is automatically generated and used. The certificate
                 is valid for the ingress controller domain (and subdomains) and the
                 generated certificate's CA will be automatically integrated with the
-                cluster's trust store. \n The in-use certificate (whether generated
-                or user-specified) will be automatically integrated with OpenShift's
-                built-in OAuth server."
+                cluster's trust store. \n If a wildcard certificate is used and shared
+                by multiple HTTP/2 enabled routes (which implies ALPN) then clients
+                (i.e., notably browsers) are at liberty to reuse open connections.
+                This means a client can reuse a connection to another route and that
+                is likely to fail. This behaviour is generally known as connection
+                coalescing. \n The in-use certificate (whether generated or user-specified)
+                will be automatically integrated with OpenShift's built-in OAuth server."
               properties:
                 name:
                   description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names

diff --git a/operator/v1/zz_generated.swagger_doc_generated.go b/operator/v1/zz_generated.swagger_doc_generated.go
diff --git a/route/v1/zz_generated.swagger_doc_generated.go b/route/v1/zz_generated.swagger_doc_generated.go