Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gep-1762: Add attachTo to in cluster deployments GEP #2945

Closed
wants to merge 1 commit into from
Closed

gep-1762: Add attachTo to in cluster deployments GEP #2945

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 31 additions & 0 deletions geps/gep-1762/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,37 @@ With this configuration, an implementation:
This is not simply `NAME` to reduce the chance of conflicts with existing resources.
Where required, this can also serve as the prefix for the object.

### Manual Deployments

A "manual deployment" allows a user to configure existing infrastructure with the Gateway API.
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` in some way.
* 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.

### Customizations

With any in-cluster deployment, customization requirements will arise.
Expand Down