Documentation: warn for disconnected Pods when deploying Azure IPAM

Signed-off-by: Timo Beckers <timo@isovalent.com>
cilium · Jan 6, 2021 · d91c7f7 · d91c7f7
1 parent 684f472
commit d91c7f7
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 0 deletions.
diff --git a/Documentation/gettingstarted/k8s-install-azure.rst b/Documentation/gettingstarted/k8s-install-azure.rst
@@ -77,6 +77,11 @@ Deploy Cilium
 
 Deploy Cilium release via Helm:
 
+.. warning::
+  Deploying Cilium with ``azure.enabled=true`` will disconnect all running Pods
+  in the cluster that were scheduled using the default ``azure-vnet`` CNI plugin.
+  We aim to remove this limitation before moving Azure IPAM out of Beta.
+
 .. parsed-literal::
 
    helm install cilium |CHART_RELEASE| \\

diff --git a/Documentation/gettingstarted/kubeproxy-free.rst b/Documentation/gettingstarted/kubeproxy-free.rst
@@ -760,6 +760,11 @@ NodePort XDP requires Cilium to run in direct routing mode (``tunnel=disabled``)
 It is recommended to use Azure IPAM for the pod IP address allocation, which
 will automatically configure your virtual network to route pod traffic correctly:
 
+.. warning::
+  Deploying Cilium with ``azure.enabled=true`` will disconnect all running Pods
+  in the cluster that were scheduled using the default ``azure-vnet`` CNI plugin.
+  We aim to remove this limitation before moving Azure IPAM out of Beta.
+
 .. parsed-literal::
 
    helm install cilium |CHART_RELEASE| \\