从 Azure Kubernetes 服务 (AKS) 群集节点获取 kubelet 日志Get kubelet logs from Azure Kubernetes Service (AKS) cluster nodes

在操作 AKS 群集的过程中，可能需要查看日志来排查问题。As part of operating an AKS cluster, you may need to review logs to troubleshoot a problem. Azure 门户内置了查看 AKS 群集中容器的日志的功能。Built-in to the Azure portal is the ability to view logs for containers in an AKS cluster. 有时，可能需要从 AKS 节点获取 kubelet 日志以进行故障排除。Occasionally, you may need to get kubelet logs from an AKS node for troubleshooting purposes.

本文介绍如何在 AJS 节点上使用 journalctl 查看 kubelet 日志。This article shows you how you can use journalctl to view the kubelet logs on an AKS node.

准备阶段Before you begin

本文假定你拥有现有的 AKS 群集。This article assumes that you have an existing AKS cluster. 如果需要 AKS 群集，请参阅 AKS 快速入门使用 Azure CLI 或使用 Azure 门户。If you need an AKS cluster, see the AKS quickstart using the Azure CLI or using the Azure portal.

创建 SSH 连接Create an SSH connection

首先，与需要在其上查看 kubelet 日志的节点建立 SSH 连接。First, create an SSH connection with the node on which you need to view kubelet logs. 在通过 SSH 登录到 Azure Kubernetes 服务 (AKS) 群集节点文档中详细介绍了此操作。This operation is detailed in the SSH into Azure Kubernetes Service (AKS) cluster nodes document.

获取 kubelet 日志Get kubelet logs

连接到节点后，运行以下命令以拉取 kubelet 日志：Once you have connected to the node, run the following command to pull the kubelet logs:

sudo journalctl -u kubelet -o cat

以下示例输出显示 kubelet 日志数据：The following sample output shows the kubelet log data:

I0508 12:26:17.905042    8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"
I0508 12:26:27.943494    8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"
I0508 12:26:28.920125    8672 server.go:796] GET /stats/summary: (10.370874ms) 200 [[Ruby] 10.244.0.2:52292]
I0508 12:26:37.964650    8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"
I0508 12:26:47.996449    8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"
I0508 12:26:58.019746    8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"
I0508 12:27:05.107680    8672 server.go:796] GET /stats/summary/: (24.853838ms) 200 [[Go-http-client/1.1] 10.244.0.3:44660]
I0508 12:27:08.041736    8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"
I0508 12:27:18.068505    8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"
I0508 12:27:28.094889    8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"
I0508 12:27:38.121346    8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"
I0508 12:27:44.015205    8672 server.go:796] GET /stats/summary: (30.236824ms) 200 [[Ruby] 10.244.0.2:52588]
I0508 12:27:48.145640    8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"
I0508 12:27:58.178534    8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"
I0508 12:28:05.040375    8672 server.go:796] GET /stats/summary/: (27.78503ms) 200 [[Go-http-client/1.1] 10.244.0.3:44660]
I0508 12:28:08.214158    8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"
I0508 12:28:18.242160    8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"
I0508 12:28:28.274408    8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"
I0508 12:28:38.296074    8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"
I0508 12:28:48.321952    8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"
I0508 12:28:58.344656    8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"