chore(module): extract kube-api-rewriter into separate project#2051
Merged
diafour merged 1 commit intoMar 4, 2026
Merged
Conversation
universal-itengineer
requested review from
nevermarine and
universal-itengineer
as code owners
- Use kube-api-rewriter machinery from the external repo - Only KubeVirt and CDI rules are needed here. Signed-off-by: Ivan Mikheykin <ivan.mikheykin@flant.com>
diafour
force-pushed
the
chore/module/move-kube-api-rewriter-to-external-repo
branch
from
c292449 to
9e291ed
Compare
universal-itengineer
approved these changes
Mar 4, 2026
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
2 participants
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
Why do we need it, and what problem does it solve?
We want to share kube-api-rewriter machinery with other modules.
What is the expected result?
KubeVirt and CDI rewrites work as expected.
Checklist
Changelog entries