Merge pull request #152992 from qpetraroia/patch-3

Add new FAQ sections as well as get rid of 1.17x on the chart

Author: PRMerger7

articles/aks/supported-kubernetes-versions.md

@@ -184,6 +184,14 @@ To upgrade, from *1.12.x* -> *1.14.x*, first upgrade from *1.12.x* -> *1.13.x*,
 
 Skipping multiple versions can only be done when upgrading from an unsupported version back into a supported version. For example, upgrade from an unsupported *1.10.x* --> a supported *1.15.x* can be completed.
 
+**Can I create a new 1.xx.x cluster during its 30 day support window?**
+
+No. Once a version is deprecated/removed, you cannot create a cluster with that version. As the change rolls out, you will start to see the old version removed from your version list. This process may take up to two weeks from announcement, progressively by region.
+
+**I am on a freshly deprecated version, can I still add new node pools? Or will I have to upgrade?**
+
+No. You will not be allowed to add node pools of the deprecated version to your cluster. You can add node pools of a new version. However, this may require you to update the control plane first. 
+
 ## Next steps
 
 For information on how to upgrade your cluster, see [Upgrade an Azure Kubernetes Service (AKS) cluster][aks-upgrade].