You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
stealthybox
changed the title
Flux export can be improved with managedFieldsflux export can be improved with managedFields
Mar 19, 2021
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.
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.
The text was updated successfully, but these errors were encountered: