When it comes to IP addresses, Kubernetes has a demand and supply issue. On the Demand side, Kubernetes treats Pods as first class citizens with their own IPs. This makes port mappings and usage from a developer’s point of view much much simpler. But from an infrastructure perspective, this makes the whole cluster use IP addresses liberally.
On the Supply side, Kubernetes deployments generally run alongside incumbent networks. Therefore there are not enough IPs to allocate and have a production grade deployment.
Based on real world experience by our customers so far, we have found that there are a few ways to design your clusters to address these concerns: -- Optimize the per node allocation so that the overall consumption can be optimized -- re-use IP addresses for Infrastructure but have unique Services IPs. -- Leverage a new IP addressing scheme through non-RFC 1918 ranges
Mahesh Narayanan is a Cloud Networking Product Manager at Google Cloud. He works on GKE and drives its networking strategy and roadmap. Mahesh has also worked in sales and customer support roles and has a good understanding of customer perspective. Prior to Google, Mahesh worked in... Read More →
Satya is a Software Engineer at Google. He lives and breathes GKE including GKE On-Prem. Satya has extensive Enterprise customer experience with stints at companies like Yahoo and Walmart.
