k8s各组件启动时, -v参数指定的日志级别

Posted chuanzhang053

tags:

篇首语:本文由小常识网(cha138.com)小编为大家整理,主要介绍了k8s各组件启动时, -v参数指定的日志级别相关的知识,希望对你有一定的参考价值。

k8s 相关组件启动时 -v参数指定的日志级别

--v=0   Generally useful for this to ALWAYS be visible to an operator.
--v=1   A reasonable default log level if you don’t want verbosity.
--v=2   Useful steady state information about the service and important log messages that may correlate to significant changes in the system. This is the recommended default log level for most systems.
--v=3   Extended information about changes.
--v=4   Debug level verbosity.
--v=6   Display requested resources.
--v=7   Display HTTP request headers.
--v=8   Display HTTP request contents

示例:

[root@node-08 ~]# cat /usr/lib/systemd/system/kubelet.service 
[Unit]
Description=Kubernetes Kubelet Server
After=docker.service
Requires=docker.service

[Service]
WorkingDirectory=/var/lib/kubelet
ExecStart=/usr/local/bin/kubelet   --kubeconfig=/root/.kube/config   --hostname-override=172.20.59.57   --pod-infra-container-image=172.20.59.190:81/k8s/pause-amd64:3.1   --logtostderr=false   --log-dir=/var/log/kubernetes   --v=4       #此处为需要配置的日志级别
Restart=on-failure

[Install]
WantedBy=multi-user.targe

以上是关于k8s各组件启动时, -v参数指定的日志级别的主要内容,如果未能解决你的问题,请参考以下文章

k8s记录-国内下载k8s组件镜像

K8S原来如此简单K8S核心组件与基本原理

k8s监控组件heapster安装部署

Kubernetes(K8s)主要组件简要介绍面试必看

k8s启动单点mysql

解决k8s核心组件calico pod资源不创建问题