-
Notifications
You must be signed in to change notification settings - Fork 41.3k
Closed
Labels
sig/cliCategorizes an issue or PR as relevant to SIG CLI.Categorizes an issue or PR as relevant to SIG CLI.wg/api-expressionCategorizes an issue or PR as relevant to WG API Expression.Categorizes an issue or PR as relevant to WG API Expression.
Description
Recently (1.18?) a new field was added to configs, managedFields. This is incredibly verbose, which makes kubectl commands like -oyaml
and edit
painful.
For example, on a random deployment I have looked at, the entire kubectl get deployment -oyaml
is 640 lines. Managed fields is over half of that, with 358 lines.
I am not sure if its feasible to somehow mitigate this without breaking server side apply or other features, but it would be useful if possible. One possible idea would be to just hide it from kubectl commands, but I am not sure the impact of that. The goal of this issue is mostly to bring awareness that this causes some user pain and see if we can improve that a bit.
Version:
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.0", GitCommit:"9e991415386e4cf155a24b1da15becaa390438d8", GitTreeState:"clean", BuildDate:"2020-03-25T14:58:59Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.0", GitCommit:"9e991415386e4cf155a24b1da15becaa390438d8", GitTreeState:"clean", BuildDate:"2020-03-25T20:56:08Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}
awillows, stigok, tamalsaha, mszostok, jasper-d and 260 morehrishin, cbluth, Chili-Man, sbuvaneshkumar, satyashr and 14 morezanetworker, zhiweiv, stevengibbszions, ringtail, nolar and 11 more
Metadata
Metadata
Assignees
Labels
sig/cliCategorizes an issue or PR as relevant to SIG CLI.Categorizes an issue or PR as relevant to SIG CLI.wg/api-expressionCategorizes an issue or PR as relevant to WG API Expression.Categorizes an issue or PR as relevant to WG API Expression.