Use kubectl describe nodes to check the OS kernel version and the OS image version of the nodes in your cluster: kubectl describe nodes Linux might receive daily security updates, but Windows Server nodes update by performing an AKS upgrade that deploys new nodes with the latest base Window Server image and patches. You can use node image upgrades to streamline upgrades for both Windows and Linux node pools, but the processes differ slightly. Using the node image upgrade method ensures you get only tested kernels and components that are compatible with those kernels. Node image updates have all relevant and validated security updates and feature updates. For more information about automating node image upgrades, see Node upgrade GitHub Actions.Īn updated node image contains up-to-date OS security patches, kernel updates, Kubernetes security updates, newer versions of binaries like kubelet, and component version updates listed in the release notes. To keep your agent node OS and runtime components patched, consider checking and applying node image upgrades every two weeks, or automating the node image upgrade process. Auto-upgrade with the node image update SKU can automate the process.ĪKS supports upgrading node images by using az aks nodepool upgrade, so you can keep up with the newest OS and runtime updates. For node image upgrade, we create a patched node every week for customers to use, which would require applying that patched virtual hard disk (VHD). You're required to use something like KURED or node image upgrade to reboot the node and complete the cycle. Unattended updates are automatic, but they don’t account for kernel level patches. For AKS Linux nodes, we have two mechanisms to patch the nodes: unattended updates and node image upgrade.
Microsoft provides patches and new images for image nodes weekly. This section of the Azure Kubernetes Service (AKS) day-2 operations guide describes patching and upgrading practices for AKS worker nodes and Kubernetes (K8S) versions.
0 kommentar(er)
