{ "componentChunkName": "component---src-templates-issues-tsx", "path": "/issues/311", "result": {"data":{"issuesJson":{"id":"0ba7c8c3-0c55-5f3f-94e5-d0ac61d196ec","title":"itaysk/kubectl-neat: 能够智能清除 kubectl get pod -o yaml 时的无用输出，使其更易于阅读","number":311,"bodyHTML":"

\n

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

Repos	itaysk/kubectl-neat
Views	$\"views\"$
Stars	$\"stars\"$
Forks	$\"forks\"$
License	$\"license\"$
UpdatedAt	$\"last-commit\"$
CreatedAt	$\"create-at\"$

\n\n

\n

\n

\n

kubectl-neat

\n

Remove clutter from Kubernetes manifests to make them more readable.

\n

Demo

\n

Here is a result of a kubectl get pod -o yaml for a simple Pod. The lines marked in red are considered redundant and will be removed from the output by kubectl-neat.

\n

\n

Why

\n

When you create a Kubernetes resource, let's say a Pod, Kubernetes adds a whole bunch of internal system information to the yaml or json that you originally authored. This includes:

\n

Metadata such as creation timestamp, or some internal IDs
Fill in for missing attributes with default values
Additional system attributes created by admission controllers, such as service account token
Status information

\n

If you try to kubectl get resources you have created, they will no longer look like what you originally authored, and will be unreadably verbose.
\nkubectl-neat cleans up that redundant information for you.

\n

Installation

\n

kubectl krew install neat

\n

or just download the binary if you prefer.

\n

When used as a kubectl plugin the command is kubectl neat, and when used as a standalone executable it's kubectl-neat.

\n

Usage

\n

There are two modes of operation that specify where to get the input document from: a local file or from Kubernetes.

\n

Local - file or Stdin

\n

This is the default mode if you run just kubectl neat. This command accepts an optional flag -f/--file which specifies the file to neat. It can be a path to a local file, or - to read the file from stdin. If omitted, it will default to -. The file must be a yaml or json file and a valid Kubernetes resource.

\n

There's another optional optional flag, -o/--output which specifies the format for the output. If omitted it will default to the same format of the input (auto-detected).

\n

Examples:

\n

kubectl get pod mypod -o yaml | kubectl neat\n\nkubectl get pod mypod -oyaml | kubectl neat -o json\n\nkubectl neat -f - <./my-pod.json\n\nkubectl neat -f ./my-pod.json\n\nkubectl neat -f ./my-pod.json --output yaml

\n

Kubernetes - kubectl get wrapper

\n

This mode is invoked by calling the get subcommand, i.e kubectl neat get .... It is a convenience to run kubectl get and then kubectl neat the output in a single command. It accepts any argument that kubectl get accepts and passes those arguments as is to kubectl get. Since it executes kubectl, it need to be able to find it in the path.

\n

Examples:

\n

kubectl neat get -- pod mypod -oyaml\nkubectl neat get -- svc -n default myservice --output json

\n

How it works

\n

Besides general tidying for status, metadata, and empty fields, kubectl-neat primarily looks for two types of things: default values inserted by Kubernetes' object model, and common mutating controllers.

\n

Kubernetes object model defaults

\n

For de-defaulting Kubernetes' object model, we invoke the same code that Kubernetes would have, and see what default values were assigned. If these observed values look like the ones we have in the incoming spec, we conclude they are default. If they weren't, and the user manually set a field to it's default value, it's not a bad thing to remove it anyway.

\n

Common mutating controllers

\n

Here are the recommended admission controllers, and their relation to kubectl-neat:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n

controller	description	neat
NamespaceLifecycle	rejects operations on resources in namespaces being deleted	ignore
LimitRanger	set default values for resource requests and limits	ignore
ServiceAccount	set default service account and assign token	Remove `default-token-*` volumes. Remove deprecated `spec.serviceAccount`
TaintNodesByCondition	automatically taint a node based on node conditions	TODO
Priority	validate priority class and add it's value	ignore
DefaultTolerationSeconds	configure pods to temporarily tolarate notready and unreachable taints	TODO
DefaultStorageClass	validate and set default storage class for new pvc	ignore
StorageObjectInUseProtection	prevent deletion of pvc/pv in use by adding a finalizer	ignore
PersistentVolumeClaimResize	enforce pvc resizing only for enabled storage classes	ignore
MutatingAdmissionWebhook	implement the mutating webhook feature	ignore
ValidatingAdmissionWebhook	implement the validating webhook feature	ignore
RuntimeClass	add pod overhead according to runtime class	TODO
ResourceQuota	implement the resource qouta feature	ignore
Kubernetes Scheduler	assign pods to nodes	Remove `spec.nodeName`

","updatedAt":"2025-05-21T16:07:39Z","upvoteCount":null,"author":{"login":"eryajf","avatarUrl":"https://avatars.githubusercontent.com/u/33259379?u=e4a4090a38ac2473aaed4ef9945233636776c6c3&v=4","url":"https://github.com/eryajf"},"category":null,"labels":{"edges":[{"node":{"name":"更多","color":"25B472"}},{"node":{"name":"K8S-Tools","color":"2d411a"}},{"node":{"name":"itaysk","color":"16ab6f"}}]},"comments":{"edges":[]}}},"pageContext":{"number":311,"previous":{"title":"aylei/kubectl-debug: 能够便捷地进行 Kubernetes 上的 Pod 排障诊断工具","number":310},"next":{"title":"ahmetb/kubectx: 在 kubectl 中更快速地切换不同集群和命名空间的方法","number":312}}}, "staticQueryHashes": ["151096407","2861350382"]}