fix: handle x-kubernetes-preserve-unknown-fields #325
Merged
+23
−0
Conversation
This file contains 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
…-fields is present
…-fields is present
…thub.com/jknutson/kro into fix/x-kubernetes-preserve-unknown-fields
a-hilaly
approved these changes
Feb 22, 2025
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.
Handle missing type in schema (generateObject) when x-kubernetes-preserve-unknown-fields is present.
CI checks are passing on my copy/fork of the repo: https://github.com/jknutson/kro/actions
I added a test, but did not include a type check; I did not feel that the goal here was to ensure a specific type.
If it would be valuable, I can add a test to ensure that we have an "object" returned.
This resolves #319; the failed RGD reconciles as soon as I start up the controller with this change.