Skip to content
Merged
Changes from all commits
Commits
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
19 changes: 9 additions & 10 deletions doc/extended-configuration-w-policy-attachments.md
Original file line number Diff line number Diff line change
Expand Up @@ -104,16 +104,15 @@ The *bifrost-gateway-controller* merges values before rendering templates
using the following order of precedence (aka. as *hierarchy* in
GEP-713):

Increasing order of precedence:

- `GatewayConfig` in same namespace as `Gateway`

- `GatewayClassConfig` in the same namespace as `Gateway` when `Gateway`
reference `GatewayClassConfig` indirectly through `GatewayClass`.

- `GatewayClassConfig` in *bifrost-gateway-controller* namespace when
`Gateway` reference `GatewayClassConfig` indirectly through
`GatewayClass`.
Increasing order of precedence for defaults, decreasing order of
precedence for override's as defined by GEP-713:

- Values from `GatewayClassBlueprint`
- Values from `GatewayClassConfig` in controller namespace (aka. global policies)
- Values from `GatewayClassConfig` in `Gateway`/`HTTPRoute` local namespace targeting namespace
- Values from `GatewayClassConfig` in `Gateway`/`HTTPRoute` local namespace targeting Gateway/HTTPRoute
- Values from `GatewayConfig` in `Gateway`/`HTTPRoute` local namespace, targeting namespace
- Values from `GatewayConfig` in `Gateway`/`HTTPRoute` local namespace, targeting `Gateway`/`HTTPRoute` resource

If there are multiple policies targeting the same resource and setting
the same variable, the result is undefined (see also [Conflict
Expand Down