Conversation
Updated the FAQ section to address a concern raised by one of the customer that why Azure can't utilize the AKS planned maintenance window for the underlying VMSS platform related maintenance.
|
@Kavya-KU : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 1b8aca1: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
There was a problem hiding this comment.
Pull request overview
Updates the AKS planned maintenance documentation FAQ to clarify that AKS planned maintenance windows don’t control Azure platform-level maintenance for the underlying VMSS.
Changes:
- Added a new FAQ entry explaining the separation between AKS planned maintenance and VMSS host/platform maintenance, including how reboot-required maintenance is communicated.
|
|
||
| ### Can Azure utilize the AKS planned maintenance window for Azure platform‑level maintenance impacting the underlying VMSS that hosts the AKS node pools? | ||
|
|
||
| No. The AKS planned maintenance window is specifically intended to schedule and control AKS cluster and node image upgrades in Azure Kubernetes Service. It does not apply to Azure platform‑level maintenance on the underlying VMSS hosting the AKS node pools, they operate independently with no direct dependency between them. |
There was a problem hiding this comment.
The sentence ends with a comma splice: "...hosting the AKS node pools, they operate...". Split into two sentences (or use a semicolon) so the relationship is grammatically correct and easier to read.
| No. The AKS planned maintenance window is specifically intended to schedule and control AKS cluster and node image upgrades in Azure Kubernetes Service. It does not apply to Azure platform‑level maintenance on the underlying VMSS hosting the AKS node pools, they operate independently with no direct dependency between them. | |
| No. The AKS planned maintenance window is specifically intended to schedule and control AKS cluster and node image upgrades in Azure Kubernetes Service. It does not apply to Azure platform‑level maintenance on the underlying VMSS hosting the AKS node pools. They operate independently with no direct dependency between them. |
| Azure periodically performs platform updates to enhance the reliability, performance, and security of the underlying host infrastructure for virtual machines. These updates may include patching software components, upgrading networking infrastructure, or decommissioning hardware. Platform maintenance can be either rebootless or require a reboot. | ||
| For maintenance events that require a reboot, customers are notified in advance through Maintenance Notifications, which include a `self‑service phase` that typically last up to four weeks. |
There was a problem hiding this comment.
A couple of grammar/style issues here: (1) Microsoft style guidance prefers "might" for possibility, so "These updates may include..." should be "might include"; (2) subject/verb agreement: "phase" is singular, so "typically last" should be "typically lasts".
| Azure periodically performs platform updates to enhance the reliability, performance, and security of the underlying host infrastructure for virtual machines. These updates may include patching software components, upgrading networking infrastructure, or decommissioning hardware. Platform maintenance can be either rebootless or require a reboot. | |
| For maintenance events that require a reboot, customers are notified in advance through Maintenance Notifications, which include a `self‑service phase` that typically last up to four weeks. | |
| Azure periodically performs platform updates to enhance the reliability, performance, and security of the underlying host infrastructure for virtual machines. These updates might include patching software components, upgrading networking infrastructure, or decommissioning hardware. Platform maintenance can be either rebootless or require a reboot. | |
| For maintenance events that require a reboot, customers are notified in advance through Maintenance Notifications, which include a `self‑service phase` that typically lasts up to four weeks. |
|
|
||
| If a newer version of the node image becomes available during the maintenance window, AKS performs a second upgrade to ensure that your node pools are running the latest version. This behavior is normal and doesn't indicate an issue. | ||
|
|
||
| ### Can Azure utilize the AKS planned maintenance window for Azure platform‑level maintenance impacting the underlying VMSS that hosts the AKS node pools? |
There was a problem hiding this comment.
The FAQ heading is very long and uses "utilize" (wordy). Consider shortening it and using "use" to improve scanability in the FAQ list (for example, "Can Azure use the AKS planned maintenance window for platform maintenance on the underlying VMSS?").
| ### Can Azure utilize the AKS planned maintenance window for Azure platform‑level maintenance impacting the underlying VMSS that hosts the AKS node pools? | |
| ### Can Azure use the AKS planned maintenance window for platform maintenance on the underlying VMSS? |
Updated the FAQ section to address a concern raised by one of the customer that why Azure can't utilize the AKS planned maintenance window for the underlying VMSS platform related maintenance.