Repository navigation
docs: propose kgateway configuration in the dCP - #12
Open
fedorenkobn wants to merge 1 commit into
Open
fedorenkobn wants to merge 1 commit into
fedorenkobn wants to merge 1 commit into
Conversation
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
force-pushed
the
docs/kgateway-dcp-configuration
branch
from
November 16, 2026 13:22
839a989 to
3867286
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Proposes ADR 0011 (status
proposed). It decides how the dCP configures kgateway in a zone while Kong is thefallback (ADR 0006).
It builds on ADR 0008, in which a kgateway controller in the gateway
operator serves the shared Route.
Proposal
instead of adding a new one.
gatewayRefkeeps pointing to Kong during the migration. The kgateway preset and itsspecial rules are removed.
Gatewayin the zonenamespace of the Route's
gatewayRef. A zone has at most one kgateway gateway entry. Routes carry no kgateway labelor annotation.
mode,supportedFeatures,matchHeaderandexcludemove into a newKgatewayRoutingresource per zone. The Zone and theGatewaykeep only fields that stayvalid after the migration. Deleting the resource is the rollback. After the migration, the resources and the CRD are
removed.
Headermode.Header→Selective→Allmaps to the rollout steps of ADR 0006.Headeris the testmode, in which every API is routed directly only with the match header.
KgatewayRoutingare removed.Considered options
kgatewayblock on the zone gateway entry, copied to theGatewayKgatewayRoutingCRD (recommended)Open points for the discussion
Gateway, listener) stays operator configuration for all zones. Do weneed a per-zone setting?
Checks
make markdown-lint