Skip to content
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

leverage managedFields #30

Open
itaysk opened this issue May 11, 2020 · 0 comments
Open

leverage managedFields #30

itaysk opened this issue May 11, 2020 · 0 comments

Comments

@itaysk
Copy link
Owner

itaysk commented May 11, 2020

interesting development in Kubernetes 1.18 - server side apply was rearchitected to track field ownership using a metadata field called managedFields. This field can be a great insight for kubectl-neat, especially when it comes to controllers, where it was hard to tell if the field was added by a controller (the should be removed), or by the user (and should be preserved) (For example: #12). we can now use the managedFields field get this information.
Another approach can be to just trim everything that's not managed by the user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant