Skip to content

Commit 4df3966

Browse files
authored
Merge pull request #49567 from iainfoulds/patch-10
[AKS] Viewing kubelet logs requires sudo
2 parents 836e811 + a7085be commit 4df3966

File tree

1 file changed

+16
-13
lines changed

1 file changed

+16
-13
lines changed

articles/aks/kubelet-logs.md

Lines changed: 16 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,36 +1,34 @@
11
---
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
44
services: container-service
55
author: iainfoulds
6-
manager: jeconnoc
76

87
ms.service: container-service
98
ms.topic: article
10-
ms.date: 05/08/2018
9+
ms.date: 08/21/2018
1110
ms.author: iainfou
12-
ms.custom: mvc
1311
---
1412

1513
# Get kubelet logs from Azure Kubernetes Service (AKS) cluster nodes
1614

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.
1816

1917
## Create an SSH connection
2018

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.
2220

2321
## Get kubelet logs
2422

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:
2624

27-
```azurecli-interactive
28-
journalctl -u kubelet -o cat
25+
```console
26+
sudo journalctl -u kubelet -o cat
2927
```
3028

31-
Sample Output:
29+
The following sample output shows the *kubelet* log data:
3230

33-
```console
31+
```
3432
I0508 12:26:17.905042 8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"
3533
I0508 12:26:27.943494 8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"
3634
I0508 12:26:28.920125 8672 server.go:796] GET /stats/summary: (10.370874ms) 200 [[Ruby] 10.244.0.2:52292]
@@ -54,5 +52,10 @@ I0508 12:28:48.321952 8672 kubelet_node_status.go:497] Using Node Hostname fr
5452
I0508 12:28:58.344656 8672 kubelet_node_status.go:497] Using Node Hostname from cloudprovider: "aks-agentpool-11482510-0"
5553
```
5654

55+
## Next steps
56+
57+
If you need additional troubleshooting information from the Kubernetes master, see [view Kubernetes master node logs in AKS][aks-master-logs].
58+
5759
<!-- LINKS - internal -->
58-
[aks-ssh]: aks-ssh.md
60+
[aks-ssh]: aks-ssh.md
61+
[aks-master-logs]: view-master-logs.md

0 commit comments

Comments
 (0)