Skip to content

Commit

Permalink
remove support for named policy attachment
Browse files Browse the repository at this point in the history
Signed-off-by: Guy Daich <guy.daich@sap.com>
  • Loading branch information
guydc committed Apr 25, 2024
1 parent 5119b33 commit 14dc027
Showing 1 changed file with 8 additions and 3 deletions.
11 changes: 8 additions & 3 deletions site/content/en/contributions/design/backend.md
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,6 @@ spec:
group: gateway.envoyproxy.io
kind: Backend
name: backend-mixed-ip-uds
sectionName: uds-be
tls:
caCertRefs:
- name: backend-tls-checks-certificate
Expand All @@ -111,9 +110,15 @@ spec:
* In some cases, Envoy Gateway may reject references to a `Backend` resource. For example, a backend with a UDS address
will be rejected on xRoute references.
* All attributes of the Envoy Gateway extended `BackendRef` resource MUST be implemented for the `Backend` resource.
* A `Backend` resource referenced by `BackendObjectReference` will be translated to Envoy Gateway's IR DestinationSetting.
As such, all `BackendAdresses` are treated as equivalent endpoints with identical weights, TLS settings, etc.
* Gateway-API and Envoy Gateway policies that attach to Services ([BackendTLSPolicy][], [BackendLBPolicy][])
MUST support attachment to the `Backend` resource in Envoy Gateway. Policies may attach to a named
section of the `Backend` resource (the `backendAddress.name` field).
MUST support attachment to the `Backend` resource in Envoy Gateway.
* Policy attachment to a named section of the `Backend` resource (the `backendAddress.name` field) is not supported at
this time. Currently, `BackendObjectReference` can only select ports, and not generic section names. Hence, a named
section of `Backend` cannot be referenced by routes, and so attachment of policies to named sections will create
translation ambiguity. Users that wish to attach policies to some of the `BackendAddresses` in a `Backend` resource
can use multiple `Backend` resources and pluralized `BackendRefs` instead.
* The `Backend` API SHOULD support other Gateway-API backend features, such as [Backend Protocol Selection][].
Translation of explicit upstream application protocol setting MUST be consistent with the existing implementation for
`Service` resources.
Expand Down

0 comments on commit 14dc027

Please sign in to comment.