Disable Kong(Cluster)Plugin Programmed status #4581
Closed
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:
Disables Kong(Cluster)Plugin status updates. Add TODOs for the relevant bug.
Which issue this PR fixes:
Multiple KIC instances in the same cluster will fight over plugin statuses because plugins have no class. We don't want them to have class, unless they're global.
Special notes for your reviewer:
Double duty as a release PR for #4582. AFAIK we're no longer doing updates other than the fixes themselves since we're now using relative tags, so the manifests remain unchanged.
A proper fix for this probably requires breaking out the plugin controller, so I think we want a hotfix for now. The feature isn't critical.
See https://github.com/Kong/kubernetes-ingress-controller/pull/4412/files for the original change. There are some other struct changes there, but AFAIK disabling the reconciler bit alone avoids the issue.
Didn't want to send this to main and backport since it touches generated code. I think we need to cherry-pick the first commit and generate separately if we don't have a more complete fix in for 2.12.There haven't been changes to the generated controllers since 2.11.0, so this one's actually fine.PR Readiness Checklist:
Complete these before marking the PR as
ready to review
:theSeparately to main only. chore(doc) add 2.11.1 changelog #4583CHANGELOG.md
release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR