From Kubernetes 1.6, Cloud Controller Manager (CCM) was introduced, which defines a set of interfaces so that different cloud providers could evolve their own implementations out of the Kubernetes release cycle. Talking to the cloud providers, you can't ignore the biggest player: Amazon Web Service. According to the Cloud Native Computing Foundation, in 2017, 63% of Kubernetes workloads run on AWS. AWS CloudProvider supports Service as Elastic Load Balancer (ELB) and Amazon Elastic Block Store (EBS) as StorageClass.

At the time this book was written, Amazon Elastic Container Service for Kubernetes (Amazon EKS) was under preview, which is a hosted Kubernetes service in AWS. Ideally, it'll have better integration with Kubernetes, such as Application Load Balancer (ALB) for Ingress, authorization, and networking. Currently in AWS, the limitation of routes per route tables in VPC is 50; it could be up to 100 as requested. However, network performance may be impacted if the routes exceed 50 according to the official documentation of AWS. While kops uses kubenet networking by default, which allocates a/24 CIDR to each node and configures the routes in route table in AWS VPC. This might lead to the performance hit if the cluster has more than 50 nodes. Using a CNI network could address this problem.