Backport: [metallb] fix CRD addresspools.metallb.io deletion #13592
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.
Description
Move the global hook to remove CRD
addresspools.metallb.io
to thed8-metallb
module.Why do we need it, and what problem does it solve?
PR #12453 implements the removal of the
addresspools.metallb.io
CRD. But if the customer uses its ownmetallb
module, the hook removes its CRD too. Now hook removes CRD only whend8-metallb
module is enabled.Why do we need it in the patch release (if we do)?
The problem affects CE edition users after upgrading to version 1.69.
Checklist
Changelog entries