logo标签列表

如何将kubectl describe的输出格式化为JSON

kubernetesoutput-formattingkubectl
65

kubectl get命令有一个-o标志来格式化输出。

是否有类似的方法来格式化kubectl describe命令的输出？

例如：

kubectl describe -o="jsonpath={...}" pods my-rc

该命令会为my-rc副本控制器中的Pod列表打印JSON格式。但-o在describe命令中不被接受。

6个回答
67

kubectl describe 不支持 -o 或其等效选项。它的设计初衷是人类可读而不是脚本友好的。你可以使用 kubectl get pods -l <selector_of_your_rc> -o <output_format> 来实现你所描述的功能，例如：


$ kubectl get pods -l app=guestbook,tier=frontend -o name
pod/frontend-a4kjz
pod/frontend-am1ua
pod/frontend-yz2dq
17

针对我的情况，我需要从服务中获取负载均衡器地址。我使用 kubectl get service 命令来实现：

$ kubectl -n <namespace> -ojson get service <service>

{
    "apiVersion": "v1",
    "kind": "Service",
    [...]
    "status": {
        "loadBalancer": {
            "ingress": [
                {
                    "hostname": "internal-xxxxxxxxxxxxxxxxxxxxxxxxxxx-yyyyyyyyyy.us-east-1.elb.amazonaws.com"
                }
     [...]
}
2

根据 kubectl help describe 的输出，看起来它不支持结构化输出：

$ kubectl help describe
Show details of a specific resource or group of resources.

This command joins many API calls together to form a detailed description of a
given resource or group of resources.

$ kubectl describe TYPE NAME_PREFIX

will first check for an exact match on TYPE and NAME_PREFIX. If no such resource
exists, it will output details for every resource that has a name prefixed with NAME_PREFIX

Possible resource types include (case insensitive): pods (po), services (svc), deployments,
replicasets (rs), replicationcontrollers (rc), nodes (no), events (ev), limitranges (limits),
persistentvolumes (pv), persistentvolumeclaims (pvc), resourcequotas (quota), namespaces (ns),
serviceaccounts, ingresses (ing), horizontalpodautoscalers (hpa), daemonsets (ds), configmaps,
componentstatuses (cs), endpoints (ep), and secrets.

Usage:
  kubectl describe (-f FILENAME | TYPE [NAME_PREFIX | -l label] | TYPE/NAME) [flags]

Examples:
# Describe a node
kubectl describe nodes kubernetes-minion-emt8.c.myproject.internal

# Describe a pod
kubectl describe pods/nginx

# Describe a pod identified by type and name in "pod.json"
kubectl describe -f pod.json

# Describe all pods
kubectl describe pods

# Describe pods by label name=myLabel
kubectl describe po -l name=myLabel

# Describe all pods managed by the 'frontend' replication controller (rc-created pods
# get the name of the rc as a prefix in the pod the name).
kubectl describe pods frontend

Flags:
  -f, --filename=[]: Filename, directory, or URL to a file containing the resource to describe
  -l, --selector="": Selector (label query) to filter on

Global Flags:
      --alsologtostderr[=false]: log to standard error as well as files
      --certificate-authority="": Path to a cert. file for the certificate authority.
      --client-certificate="": Path to a client certificate file for TLS.
      --client-key="": Path to a client key file for TLS.
      --cluster="": The name of the kubeconfig cluster to use
      --context="": The name of the kubeconfig context to use
      --insecure-skip-tls-verify[=false]: If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure.
      --kubeconfig="": Path to the kubeconfig file to use for CLI requests.
      --log-backtrace-at=:0: when logging hits line file:N, emit a stack trace
      --log-dir="": If non-empty, write log files in this directory
      --log-flush-frequency=5s: Maximum number of seconds between log flushes
      --logtostderr[=true]: log to standard error instead of files
      --match-server-version[=false]: Require server version to match client version
      --namespace="": If present, the namespace scope for this CLI request.
      --password="": Password for basic authentication to the API server.
  -s, --server="": The address and port of the Kubernetes API server
      --stderrthreshold=2: logs at or above this threshold go to stderr
      --token="": Bearer token for authentication to the API server.
      --user="": The name of the kubeconfig user to use
      --username="": Username for basic authentication to the API server.
      --v=0: log level for V logs
      --vmodule=: comma-separated list of pattern=N settings for file-filtered logging
0

有一种简单的方法可能会有所帮助。

您可以运行以下命令以获取服务的yaml文件。然后将其复制粘贴到一个新文件中。

kubectl edit svc {xx-servcice} -n {namespace} -o yaml
-3

正如@janekuto所建议的

describe不能用于以json格式显示数据

请查看我的答案这里。 jq是一个非常强大的实用程序，可以轻松处理kubectl的json显示。您可以在不费太多力气的情况下使用jq做很多事情。

kubectl - 以json格式格式化资源配额值

好的，我也说了同样的话，并建议使用链接 https://stackoverflow.com/questions/56250571/kubectl-format-the-resource-quota-values-in-json-format/56251508#56251508。 - nagendra547
1
如果您首先能够以JSON格式获取描述输出... - scravy
-3

kubectl不支持在describe命令中使用-o yaml/json选项，但您仍然可以使用其他一些命令来获取describe中的信息，例如：

kubectl get events
网页内容由stack overflow 提供, 点击上面的
可以查看英文原文，
原文链接