Skip to content

Commit f302940

Browse files
authored
fix column formatting in table
to use consistent alignment in table columns
1 parent c46bbed commit f302940

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/aks/azure-cni-overlay.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ Ingress connectivity to the cluster can be achieved using an ingress controller
4141
Like Azure CNI Overlay, Kubenet assigns IP addresses to pods from an address space logically different from the VNet but has scaling and other limitations. The below table provides a detailed comparison between Kubenet and Azure CNI Overlay. If you do not want to assign VNet IP addresses to pods due to IP shortage, then Azure CNI Overlay is the recommended solution.
4242

4343
| Area | Azure CNI Overlay | Kubenet |
44-
| -- | :--: | -- |
44+
| -- | -- | -- |
4545
| Cluster scale | 1000 nodes and 250 pods/node | 400 nodes and 250 pods/node |
4646
| Network configuration | Simple - no additional configuration required for pod networking | Complex - requires route tables and UDRs on cluster subnet for pod networking |
4747
| Pod connectivity performance | Performance on par with VMs in a VNet | Additional hop adds minor latency |

0 commit comments

Comments
 (0)