Skip to content

docs: propose kgateway configuration in the dCP - #12

Open
fedorenkobn wants to merge 1 commit into
mainfrom
docs/kgateway-dcp-configuration
Open

fedorenkobn wants to merge 1 commit into
mainfrom
docs/kgateway-dcp-configuration

Conversation

@fedorenkobn

Copy link
Copy Markdown

Summary

Proposes ADR 0011 (status proposed). It decides how the dCP configures kgateway in a zone while Kong is the
fallback (ADR 0006).
It builds on ADR 0008, in which a kgateway controller in the gateway
operator serves the shared Route.

Proposal

  • Presets do not change. A preset is an entry point, and kgateway takes over the ingress for the existing hostnames
    instead of adding a new one. gatewayRef keeps pointing to Kong during the migration. The kgateway preset and its
    special rules are removed.
  • No explicit link between kgateway and Kong. The kgateway controller finds the kgateway Gateway in the zone
    namespace of the Route's gatewayRef. A zone has at most one kgateway gateway entry. Routes carry no kgateway label
    or annotation.
  • Routing settings in a separate CRD (recommended option C). mode, supportedFeatures, matchHeader and
    exclude move into a new KgatewayRouting resource per zone. The Zone and the Gateway keep only fields that stay
    valid after the migration. Deleting the resource is the rollback. After the migration, the resources and the CRD are
    removed.
  • New Header mode. Header → Selective → All maps to the rollout steps of ADR 0006. Header is the test
    mode, in which every API is routed directly only with the match header.
  • End state: the presets point to the kgateway gateway entry, and the Kong entry and KgatewayRouting are removed.

Considered options

Option Where the routing settings live
A kgateway preset plus the gateway entry (today)
B kgateway block on the zone gateway entry, copied to the Gateway
C separate KgatewayRouting CRD (recommended)

Open points for the discussion

  • Do we agree on C, or do we prefer B to keep the configuration in one resource?
  • The data-plane target (namespace, Gateway API Gateway, listener) stays operator configuration for all zones. Do we
    need a per-zone setting?
  • A per-API switch back to test mode (ADR 0006, step 8) is not part of this proposal.
  • Who owns the Route status when both controllers serve a Route is discussed separately in ADR 0008.

Checks

  • make markdown-lint

@fedorenkobn
fedorenkobn requested a review from a team as a code owner November 16, 2026 13:13
Propose where the dCP configures kgateway during the migration to
kgateway with Kong as fallback. Presets and their gatewayRef stay
unchanged, and Routes carry no kgateway marker. The kgateway
controller finds the kgateway Gateway of a zone through the Route's
namespace.

Compare three places for the routing settings (mode, supportedFeatures,
matchHeader, exclude): the kgateway preset, the zone gateway entry and
a separate KgatewayRouting CRD. Recommend the CRD, so the settings can
be removed after the migration without changing the Zone API. Add the
Header mode as the test mode of the rollout.
@fedorenkobn
fedorenkobn force-pushed the docs/kgateway-dcp-configuration branch from 839a989 to 3867286 Compare November 16, 2026 13:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant