Removing BackendPolicy

This is part of the GEP kubernetes-sigs#713 implementation.
robscott · Jul 27, 2021 · 80e72bd · 80e72bd
1 parent a28d159
commit 80e72bd
Show file tree

Hide file tree

Showing 23 changed files with 14 additions and 1,203 deletions.
diff --git a/apis/v1alpha2/backendpolicy_types.go b/apis/v1alpha2/backendpolicy_types.go
diff --git a/apis/v1alpha2/httproute_types.go b/apis/v1alpha2/httproute_types.go
@@ -743,14 +743,8 @@ type HTTPRouteForwardTo struct {
 	// The gateway status for this route should be updated with a
 	// condition that describes the error more specifically.
 	//
-	// The protocol to use should be specified with the AppProtocol field on Service
-	// resources. This field was introduced in Kubernetes 1.18. If using an earlier version
-	// of Kubernetes, a `gateway.networking.k8s.io/app-protocol` annotation on the
-	// BackendPolicy resource may be used to define the protocol. If the
-	// AppProtocol field is available, this annotation should not be used. The
-	// AppProtocol field, when populated, takes precedence over the annotation
-	// in the BackendPolicy resource. For custom backends, it is encouraged to
-	// add a semantically-equivalent field in the Custom Resource Definition.
+	// The protocol to use should be specified with the AppProtocol field on
+	// Service resources.
 	//
 	// Support: Core
 	//

diff --git a/apis/v1alpha2/shared_types.go b/apis/v1alpha2/shared_types.go
@@ -32,23 +32,6 @@ const (
 	GatewayAllowSameNamespace GatewayAllowType = "SameNamespace"
 )
 
-const (
-	// AnnotationAppProtocol defines the protocol a Gateway should use for
-	// communication with a Kubernetes Service. This annotation must be present
-	// on the BackendPolicy resource and the protocol will apply to all Service
-	// ports that are selected by BackendPolicy.Spec.BackendRefs. If the
-	// AppProtocol field is available, this annotation should not be used. The
-	// AppProtocol field, when populated, takes precedence over this annotation.
-	// The value of this annotation must be also be a valid value for the
-	// AppProtocol field.
-	//
-	// Examples:
-	//
-	// - `gateway.networking.k8s.io/app-protocol: https`
-	// - `gateway.networking.k8s.io/app-protocol: tls`
-	AnnotationAppProtocol = "gateway.networking.k8s.io/app-protocol"
-)
-
 // RouteGateways defines which Gateways will be able to use a route. If this
 // field results in preventing the selection of a Route by a Gateway, an
 // "Admitted" condition with a status of false must be set for the Gateway on
@@ -106,14 +89,8 @@ type RouteForwardTo struct {
 	// with the "DegradedRoutes" reason. The gateway status for this route should
 	// be updated with a condition that describes the error more specifically.
 	//
-	// The protocol to use is defined using AppProtocol field (introduced in
-	// Kubernetes 1.18) in the Service resource. In the absence of the
-	// AppProtocol field a `gateway.networking.k8s.io/app-protocol` annotation on the
-	// BackendPolicy resource may be used to define the protocol. If the
-	// AppProtocol field is available, this annotation should not be used. The
-	// AppProtocol field, when populated, takes precedence over the annotation
-	// in the BackendPolicy resource. For custom backends, it is encouraged to
-	// add a semantically-equivalent field in the Custom Resource Definition.
+	// The protocol to use should be specified with the AppProtocol field on
+	// Service resources.
 	//
 	// Support: Core
 	//

diff --git a/apis/v1alpha2/zz_generated.deepcopy.go b/apis/v1alpha2/zz_generated.deepcopy.go
diff --git a/apis/v1alpha2/zz_generated.register.go b/apis/v1alpha2/zz_generated.register.go