You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/aks/kubelet-logs.md
+16-13Lines changed: 16 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,36 +1,34 @@
1
1
---
2
-
title: Get kubelet logs from Azure Kubernetes Service (AKS)
3
-
description: Get kubelet logs from Azure Kubernetes Service (AKS) cluster nodes
2
+
title: View kubelet logs in Azure Kubernetes Service (AKS)
3
+
description: How to view troubleshooting information in the kubelet logs from Azure Kubernetes Service (AKS) nodes
4
4
services: container-service
5
5
author: iainfoulds
6
-
manager: jeconnoc
7
6
8
7
ms.service: container-service
9
8
ms.topic: article
10
-
ms.date: 05/08/2018
9
+
ms.date: 08/21/2018
11
10
ms.author: iainfou
12
-
ms.custom: mvc
13
11
---
14
12
15
13
# Get kubelet logs from Azure Kubernetes Service (AKS) cluster nodes
16
14
17
-
Occasionally, you may need to get kubelet logs from an Azure Kubernetes Service (AKS) node for troubleshooting purposes. This document details one option for pulling these logs.
15
+
Occasionally, you may need to get *kubelet* logs from an Azure Kubernetes Service (AKS) node for troubleshooting purposes. This article shows you how you can use `journalctl` to view the *kubelet* logs.
18
16
19
17
## Create an SSH connection
20
18
21
-
First, create an SSH connection with the node on which you need to pull kubelet logs. This operation is detailed in the [SSH into Azure Kubernetes Service (AKS) cluster nodes][aks-ssh] document.
19
+
First, create an SSH connection with the node on which you need to view *kubelet* logs. This operation is detailed in the [SSH into Azure Kubernetes Service (AKS) cluster nodes][aks-ssh] document.
22
20
23
21
## Get kubelet logs
24
22
25
-
Once you have connected to the node, run the following command to pull the kubelet logs.
23
+
Once you have connected to the node, run the following command to pull the *kubelet* logs:
26
24
27
-
```azurecli-interactive
28
-
journalctl -u kubelet -o cat
25
+
```console
26
+
sudo journalctl -u kubelet -o cat
29
27
```
30
28
31
-
Sample Output:
29
+
The following sample output shows the *kubelet* log data:
32
30
33
-
```console
31
+
```
34
32
I0508 12:26:17.905042 8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"
35
33
I0508 12:26:27.943494 8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"
36
34
I0508 12:26:28.920125 8672 server.go:796] GET /stats/summary: (10.370874ms) 200 [[Ruby] 10.244.0.2:52292]
0 commit comments