Update gateway-api from v1alpha2 to v1beta1

Author: lucacome

deploy/manifests/gatewayclass.yaml

@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha2
+apiVersion: gateway.networking.k8s.io/v1beta1
 kind: GatewayClass
 metadata:
   name: nginx

design/archive/gateway-evaluation.md

@@ -33,7 +33,7 @@ The Gateway evaluation will employ each in the following manner:
 
 Gateway evaluation requires supplemental resources; other Core API resources are needed to complete traffic routing between an ingress point and the final backend Pod endpoints. Required supplemental resources are:
 * Services: The AppDev controls the resource lifecycle and is responsible for creating, updating, and deleting Service resources. Kubernetes Service resources describe a logical collection of like processes and act as a load balancing primitive. AppDevs create Service resources to describe their product subsystems, Services act as an abstraction for a set of real backend processes that can serve requests.
-* Endpoints: Kubernetes controllers manage Endpoint resources, Endpoints provide the association between Service abstractions and real servers. Gateway evaluation will watch Endpoints to discover upstream addresses. When AppDevs create Service and HTTPRoute objects, Gateway evaluation uses references in the HTTPRoute (via a HTTPRouteRules and HTTPBackendRefs (see [HTTP Routing](https://gateway-api.sigs.k8s.io/v1alpha2/guides/http-routing/) for more detail)) to discover the Pod IP endpoints, i.e. Gateway evaluation uses Endpoints resources, referred to by HTTPRoutes, to link routing rules to upstream addresses.
+* Endpoints: Kubernetes controllers manage Endpoint resources, Endpoints provide the association between Service abstractions and real servers. Gateway evaluation will watch Endpoints to discover upstream addresses. When AppDevs create Service and HTTPRoute objects, Gateway evaluation uses references in the HTTPRoute (via a HTTPRouteRules and HTTPBackendRefs (see [HTTP Routing](https://gateway-api.sigs.k8s.io/guides/http-routing/) for more detail)) to discover the Pod IP endpoints, i.e. Gateway evaluation uses Endpoints resources, referred to by HTTPRoutes, to link routing rules to upstream addresses.
 
 ### Goals
 - Vet a minimal feature set of Core resources for their applicability and conformance to NGINX configuration models.

examples/advanced-routing/cafe-routes.yaml

@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha2
+apiVersion: gateway.networking.k8s.io/v1beta1
 kind: HTTPRoute
 metadata:
   name: coffee
@@ -33,7 +33,7 @@ spec:
     - name: coffee-v2-svc
       port: 80
 ---
-apiVersion: gateway.networking.k8s.io/v1alpha2
+apiVersion: gateway.networking.k8s.io/v1beta1
 kind: HTTPRoute
 metadata:
   name: tea

examples/advanced-routing/gateway.yaml

@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha2
+apiVersion: gateway.networking.k8s.io/v1beta1
 kind: Gateway
 metadata:
   name: gateway

examples/cafe-example/cafe-routes.yaml

@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha2
+apiVersion: gateway.networking.k8s.io/v1beta1
 kind: HTTPRoute
 metadata:
   name: cafe
@@ -13,7 +13,7 @@ spec:
     - name: main
       port: 80
 ---
-apiVersion: gateway.networking.k8s.io/v1alpha2
+apiVersion: gateway.networking.k8s.io/v1beta1
 kind: HTTPRoute
 metadata:
   name: coffee
@@ -32,7 +32,7 @@ spec:
     - name: coffee
       port: 80
 ---
-apiVersion: gateway.networking.k8s.io/v1alpha2
+apiVersion: gateway.networking.k8s.io/v1beta1
 kind: HTTPRoute
 metadata:
   name: tea

examples/cafe-example/gateway.yaml

@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha2
+apiVersion: gateway.networking.k8s.io/v1beta1
 kind: Gateway
 metadata:
   name: gateway

examples/https-termination/cafe-routes.yaml

@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha2
+apiVersion: gateway.networking.k8s.io/v1beta1
 kind: HTTPRoute
 metadata:
   name: coffee
@@ -17,7 +17,7 @@ spec:
     - name: coffee
       port: 80
 ---
-apiVersion: gateway.networking.k8s.io/v1alpha2
+apiVersion: gateway.networking.k8s.io/v1beta1
 kind: HTTPRoute
 metadata:
   name: tea

examples/https-termination/gateway.yaml

@@ -1,4 +1,4 @@
-apiVersion: gateway.networking.k8s.io/v1alpha2
+apiVersion: gateway.networking.k8s.io/v1beta1
 kind: Gateway
 metadata:
   name: gateway

internal/events/event.go

@@ -15,6 +15,6 @@ type UpsertEvent struct {
 type DeleteEvent struct {
 	// NamespacedName is the namespace & name of the deleted resource.
 	NamespacedName types.NamespacedName
-	// Type is the resource type. For example, if the event is for *v1alpha2.HTTPRoute, pass &v1alpha2.HTTPRoute{} as Type.
+	// Type is the resource type. For example, if the event is for *v1beta1.HTTPRoute, pass &v1beta1.HTTPRoute{} as Type.
 	Type client.Object
 }

internal/events/loop.go

@@ -6,7 +6,7 @@ import (
 
 	"github.com/go-logr/logr"
 	apiv1 "k8s.io/api/core/v1"
-	"sigs.k8s.io/gateway-api/apis/v1alpha2"
+	"sigs.k8s.io/gateway-api/apis/v1beta1"
 
 	"github.com/nginxinc/nginx-kubernetes-gateway/internal/nginx/config"
 	"github.com/nginxinc/nginx-kubernetes-gateway/internal/nginx/file"
@@ -125,11 +125,11 @@ func (el *EventLoop) updateNginx(ctx context.Context, conf state.Configuration)
 
 func (el *EventLoop) propagateUpsert(e *UpsertEvent) {
 	switch r := e.Resource.(type) {
-	case *v1alpha2.GatewayClass:
+	case *v1beta1.GatewayClass:
 		el.cfg.Processor.CaptureUpsertChange(r)
-	case *v1alpha2.Gateway:
+	case *v1beta1.Gateway:
 		el.cfg.Processor.CaptureUpsertChange(r)
-	case *v1alpha2.HTTPRoute:
+	case *v1beta1.HTTPRoute:
 		el.cfg.Processor.CaptureUpsertChange(r)
 	case *apiv1.Service:
 		// FIXME(pleshakov): make sure the affected hosts are updated
@@ -144,11 +144,11 @@ func (el *EventLoop) propagateUpsert(e *UpsertEvent) {
 
 func (el *EventLoop) propagateDelete(e *DeleteEvent) {
 	switch e.Type.(type) {
-	case *v1alpha2.GatewayClass:
+	case *v1beta1.GatewayClass:
 		el.cfg.Processor.CaptureDeleteChange(e.Type, e.NamespacedName)
-	case *v1alpha2.Gateway:
+	case *v1beta1.Gateway:
 		el.cfg.Processor.CaptureDeleteChange(e.Type, e.NamespacedName)
-	case *v1alpha2.HTTPRoute:
+	case *v1beta1.HTTPRoute:
 		el.cfg.Processor.CaptureDeleteChange(e.Type, e.NamespacedName)
 	case *apiv1.Service:
 		// FIXME(pleshakov): make sure the affected hosts are updated