Fix incorrect spec change for Policy objects (#4304)

This commit fixes a change made in error to the XBackendTrafficPolicy
object, and moves that change to the BackendTLSPolicy object.

The change in question marks the supported number of targetRefs
for BackendTLSPolicy as one, until we can talk through edge cases
in targetRef handling and status updates.

Signed-off-by: Nick Young <[email protected]>

Author: youngnick

apis/v1/backendtlspolicy_types.go

@@ -88,6 +88,12 @@ type BackendTLSPolicySpec struct {
 	// implementation MUST ensure the `Accepted` Condition is set to
 	// `status: False`, with Reason `Conflicted`.
 	//
+	// Implementations SHOULD NOT support more than one targetRef at this
+	// time. Although the API technically allows for this, the current guidance
+	// for conflict resolution and status handling is lacking. Until that can be
+	// clarified in a future release, the safest approach is to support a single
+	// targetRef.
+	//
 	// Support: Extended for Kubernetes Service
 	//
 	// Support: Implementation-specific for any other resource

apisx/v1alpha1/xbackendtrafficpolicy_types.go

@@ -69,10 +69,6 @@ type BackendTrafficPolicySpec struct {
 	// Currently, a TargetRef can not be scoped to a specific port on a
 	// Service.
 	//
-	// Because of concerns over recording status correctly in some edge cases,
-	// currently, Core support is only given to one (1) TargetRef. More than
-	// one TargetRef is Implementation Specific.
-	//
 	// +listType=map
 	// +listMapKey=group
 	// +listMapKey=kind