Changes HTTPRoute hostname field to be singular

Author: danehans

api/v1alpha1/httproute_types.go

@@ -34,11 +34,24 @@ type HTTPRouteSpec struct {
 
 // HTTPRouteHost is the configuration for a given host.
 type HTTPRouteHost struct {
-	// Hostnames are a list of hosts names that match this host
-	// block.
+	// Hostname 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 the RFC:
 	//
-	// TODO: RFC link
-	Hostnames []string `json:"hostnames"`
+	// 1. IPs are not allowed.
+	// 2. The `:` delimiter is not respected because ports are not allowed.
+	//
+	// Incoming requests are matched against Hostname before processing HTTPRoute
+	// rules. For example, if the request header contains host: foo.example.com,
+	// an HTTPRoute with hostname foo.example.com will match. However, an
+	// HTTPRoute with hostname example.com or bar.example.com will not match.
+	// If Hostname is unspecified, the Gateway routes all traffic based on
+	// the specified rules.
+	//
+	// Support: Core
+	//
+	// +optional
+	Hostname string `json:"hostname,omitempty"`
 
 	// Rules are a list of HTTP matchers, filters and actions.
 	Rules []HTTPRouteRule `json:"rules"`

api/v1alpha1/zz_generated.deepcopy.go

@@ -58,12 +58,19 @@ spec:
                   - kind
                   - name
                   type: object
-                hostnames:
-                  description: "Hostnames are a list of hosts names that match this
-                    host block. \n TODO: RFC link"
-                  items:
-                    type: string
-                  type: array
+                hostname:
+                  description: "Hostname 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 the RFC: \n 1. IPs
+                    are not allowed. 2. The `:` delimiter is not respected because
+                    ports are not allowed. \n Incoming requests are matched against
+                    Hostname before processing HTTPRoute rules. For example, if the
+                    request header contains host: foo.example.com, an HTTPRoute with
+                    hostname foo.example.com will match. However, an HTTPRoute with
+                    hostname example.com or bar.example.com will not match. If Hostname
+                    is unspecified, the Gateway routes all traffic based on the specified
+                    rules. \n Support: Core"
+                  type: string
                 rules:
                   description: Rules are a list of HTTP matchers, filters and actions.
                   items:
@@ -217,7 +224,6 @@ spec:
                     type: object
                   type: array
               required:
-              - hostnames
               - rules
               type: object
             hosts:
@@ -245,12 +251,19 @@ spec:
                     - kind
                     - name
                     type: object
-                  hostnames:
-                    description: "Hostnames are a list of hosts names that match this
-                      host block. \n TODO: RFC link"
-                    items:
-                      type: string
-                    type: array
+                  hostname:
+                    description: "Hostname 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 the RFC: \n
+                      1. IPs are not allowed. 2. The `:` delimiter is not respected
+                      because ports are not allowed. \n Incoming requests are matched
+                      against Hostname before processing HTTPRoute rules. For example,
+                      if the request header contains host: foo.example.com, an HTTPRoute
+                      with hostname foo.example.com will match. However, an HTTPRoute
+                      with hostname example.com or bar.example.com will not match.
+                      If Hostname is unspecified, the Gateway routes all traffic based
+                      on the specified rules. \n Support: Core"
+                    type: string
                   rules:
                     description: Rules are a list of HTTP matchers, filters and actions.
                     items:
@@ -416,7 +429,6 @@ spec:
                       type: object
                     type: array
                 required:
-                - hostnames
                 - rules
                 type: object
               type: array