Drop attachTo

Author: howardjohn

geps/gep-1762.md

@@ -66,32 +66,7 @@ With this configuration, an implementation:
 
 ### Manual Deployments
 
-When a manual deployment is used, a user must explicitly link their Gateway to existing infrastructure. This is done by specifying `spec.infrastructure.attachTo`.
-
-For the common case that the "existing infrastructure" is a `Service`:
-
-```yaml
-apiVersion: gateway.networking.k8s.io/v1beta1
-kind: Gateway
-metadata:
-  name: my-gateway
-spec:
-  infrastructure:
-    attachTo:
-      kind: Service
-      name: existing-service
-  gatewayClassName: example
-  listeners:
-  - name: default
-    port: 80
-    protocol: HTTP
-```
-
-With this configuration, an implementation:
-* MUST provide an address in `Status.Addresses` where the Gateway can be reached.
-  This MUST be derived from the referenced `spec.infrastructure.attachTo`.
-* MUST not deploy any resources into the cluster; it is expected that a user will do these actions.
-* MUST reject any other `infrastructure` fields (see [GEP-1867](https://gateway-api.sigs.k8s.io/geps/gep-1867/#api)) being configured; these will not be respected.
+Managing "Manual Deployments" is currently out of scope for this GEP, but may be added in the future.
 
 ### Customizations
 
@@ -261,21 +236,6 @@ type GatewayInfrastructure struct {
   //
 	// Support: Implementation-specific
 	Annotations map[string]string `json:"annotations,omitempty"`
-	// AttachTo is an optional, implementation-specific way to attach a Gateway to some existing infrastructure.
-	// For in-cluster deployments, implementations MAY allow attaching to an existing `Service` object.
-	//
-	// When this field is set, an implementation:
-	// * MUST continue to provide an address in `Status.Addresses` where the Gateway can be reached. This SHOULD be
-	//   derived from the referenced `spec.infrastructure.attachTo` object, if applicable.
-	// * If the presence of an `attachTo` means new infrastructure will not be provisioned, an implementation MUST reject
-	//   any other `infrastructure` fields that will not be respected as a result.
-	// * For in-cluster implementations referencing `Service`
-	//   * MUST not create or modify compute resources (such as `Deployment` or `Service`) into the cluster; it is expected that a user will do these actions.
-	//
-	// Support: Implementation-specific
-	//
-	// +optional
-	AttachTo []LocalObjectReference `json:"attachTo,omitempty"`
 	// ParametersRef is a reference to a resource that contains the configuration
 	// parameters corresponding to the Gateway. This is optional if the
 	// controller does not require any additional configuration.