Skip to content

Commit e209121

Browse files
authored
Update concepts-vulnerability-management.md
1 parent 955ab6a commit e209121

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/aks/concepts-vulnerability-management.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Vulnerability management for Azure Kubernetes Service
33
titleSuffix: Azure Kubernetes Service
44
description: Learn how Microsoft manages security vulnerabilities for Azure Kubernetes Service (AKS) clusters.
55
ms.topic: conceptual
6-
ms.date: 02/24/2023
6+
ms.date: 03/02/2023
77

88
---
99

@@ -51,7 +51,7 @@ Each evening, Linux nodes in AKS receive security patches through their distribu
5151

5252
Nightly, we apply security updates to the OS on the node, but the node image used to create nodes for your cluster remains unchanged. If a new Linux node is added to your cluster, the original image is used to create the node. This new node receives all the security and kernel updates available during the automatic assessment performed every night, but remains unpatched until all checks and restarts are complete. You can use node image upgrade to check for and update node images used by your cluster. For more information on node image upgrade, see [Azure Kubernetes Service (AKS) node image upgrade][aks-node-image-upgrade].
5353

54-
For AKS clusters on the OS auto upgrade channel, the unattended upgrade process is disabled, and the OS nodes will receive security updates through the weekly node image upgrade.
54+
For AKS clusters on the [OS auto upgrade](https://learn.microsoft.com/en-us/azure/aks/auto-upgrade-node-image) channel, the unattended upgrade process is disabled, and the OS nodes will receive security updates through the weekly node image upgrade.
5555

5656
### Windows Server nodes
5757

0 commit comments

Comments
 (0)