Skip to content

Commit e03437b

Browse files
Merge pull request #122821 from JoeyC-Dev/patch-3
Simple fix
2 parents 36997e4 + 7cb6396 commit e03437b

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/aks/concepts-vulnerability-management.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ The following table describes vulnerability severity categories:
7777

7878
AKS patches Common Vulnerabilities and Exposures (CVEs) that have a *vendor fix* every week. Any CVEs without a fix are waiting on a vendor fix before they can be remediated. The fixed container images are cached in the next corresponding virtual hard disk (VHD) build, which also contains the updated Ubuntu/Azure Linux/Windows patched CVEs. As long as you're running the updated VHD, you shouldn't be running any container image CVEs with a vendor fix that is over 30 days old.
7979

80-
For the OS-based vulnerabilities in the VHD, AKS also relies on node image vhd updates by default, so any security updates will come with weekly node image releases . Unattended upgrades is disabled unless you switch to unmanaged which is not recommended as its release is global.
80+
For the OS-based vulnerabilities in the VHD, AKS also relies on node image vhd updates by default, so any security updates will come with weekly node image releases. Unattended upgrades is disabled unless you switch to unmanaged which is not recommended as its release is global.
8181

8282
## Update release timelines
8383

@@ -103,7 +103,7 @@ Include the following requested information (as much as you can provide) to help
103103
* Any special configuration required to reproduce the issue
104104
* Step-by-step instructions to reproduce the issue
105105
* Proof-of-concept or exploit code (if possible)
106-
* Impact of the issue, including how an attacker might exploit the issue.
106+
* Impact of the issue, including how an attacker might exploit the issue
107107

108108
This information helps us triage your reported security issue quicker.
109109

articles/aks/supported-kubernetes-versions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -310,15 +310,15 @@ To upgrade from *1.27.x* -> *1.29.x*:
310310

311311
Skipping multiple versions can only be done when upgrading from an unsupported version back into the minimum supported version. For example, you can upgrade from an unsupported *1.25.x* to a supported *1.27.x* if *1.27* is the minimum supported minor version.
312312

313-
When performing an upgrade from an _unsupported version_ that skips two or more minor versions, the upgrade is performed without any guarantee of functionality and is excluded from the service-level agreements and limited warranty.Clusters running _unsupported version_ has the flexibility of decoupling control plane upgrades with node pool upgrades. However if your version is significantly out of date, we recommend that you re-create the cluster.
313+
When performing an upgrade from an _unsupported version_ that skips two or more minor versions, the upgrade is performed without any guarantee of functionality and is excluded from the service-level agreements and limited warranty. Clusters running _unsupported version_ has the flexibility of decoupling control plane upgrades with node pool upgrades. However if your version is significantly out of date, we recommend that you re-create the cluster.
314314

315315
### Can I create a new 1.xx.x cluster during its 30 day support window?
316316

317317
No. Once a version is deprecated/removed, you can't create a cluster with that version. As the change rolls out, you'll start to see the old version removed from your version list. This process might take up to two weeks from announcement, progressively by region.
318318

319319
### I'm on a freshly deprecated version, can I still add new node pools? Or will I have to upgrade?
320320

321-
No. You aren't allowed to add node pools of the deprecated version to your cluster. Creation or upgrade of node pools upto the _unsupported version_ control plane version is allowed , irrespective of version difference between node pool and the control plane. Only alias minor upgrades are allowed.
321+
No. You aren't allowed to add node pools of the deprecated version to your cluster. Creation or upgrade of node pools upto the _unsupported version_ control plane version is allowed, irrespective of version difference between node pool and the control plane. Only alias minor upgrades are allowed.
322322

323323
### How often do you update patches?
324324

0 commit comments

Comments
 (0)