-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use NewUniqueName #2137
Use NewUniqueName #2137
Conversation
Does the PR have any schema changes?Looking good! No breaking changes found. |
I think the fieldManager name should be resolvable in Check. It works similarly to resource auto-naming, where a user can explicitly specify a value, but one is auto-assigned otherwise. |
Does the PR have any schema changes?Looking good! No breaking changes found. |
Does the PR have any schema changes?Looking good! No breaking changes found. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good minus needing a changelog entry
Does the PR have any schema changes?Looking good! No breaking changes found. |
This updates the k8s provider to use NewUniqueName, the new autonaming system compatible with update plans. There are some questions of how to resolve the fact that the field manager name doesn't get resolved in Check, this will break update plans as is.