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

flux export can be improved with managedFields #1127

Open
stealthybox opened this issue Mar 19, 2021 · 1 comment
Open

flux export can be improved with managedFields #1127

stealthybox opened this issue Mar 19, 2021 · 1 comment

Comments

@stealthybox
Copy link
Member

stealthybox commented Mar 19, 2021

Currently, flux export seems to write out every field. It doesn't even omit defaults.
It looks possible to only print the fields that were specified by kubectl.

This should probably be an optional feature because of the danger of missing things.
The option could take a comma-separated list of field owners to print. There could be a reasonable default.
This would allow us to have configurable field owners in flux-cli, kustomize-controller, or helm-controller in the future.

@stealthybox stealthybox changed the title Flux export can be improved with managedFields flux export can be improved with managedFields Mar 19, 2021
@stealthybox
Copy link
Member Author

Maybe flux create ... commands could also print a message encouraging you to add the YAML to your repo?
There could be an -o=yaml or an --output-file flag for scripting/automation.

It's a bit awkward to throw away the client-generated object when the object exported from the cluster has many extra fields that don't fully capture the intent necessarily.

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