fix: map KongConsumer
to respective KongConsumerGroup
in Konnect
#7144
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.
What this PR does / why we need it:
KIC
3.0.3
was the last without feature gateSanitizeKonnectConfigDumps=true
by default (everything works as expected).For newer versions mapping of
KongConsumer
s to respectiveKongConsumersGroup
is broken because the code responsible for sanitization omits consumer groups by mistake.This field is crucial for proper mapping, see how the config is generated
kubernetes-ingress-controller/internal/dataplane/deckgen/generate.go
Lines 152 to 166 in ff2a3d9
Which issue this PR fixes:
fixes #7143
PR Readiness Checklist:
Complete these before marking the PR as
ready to review
:CHANGELOG.md
release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR