Skip to main content

Networking Details

AWS Vanilla K8s Cluster Deployment (Self-Managed)​

AWS SelfManged K8s Cluster Networking Architecture

The architecture diagram above illustrates the networking setup for AWS Self-Managed Kubernetes (K8s) clusters. Whenever an Application Load Balancer (ALB) or Network Load Balancer (NLB) is created, it is provisioned in the public subnets. For the K8s API Server is backed by a Network Load Balancer (NLB) and the control plane is deployed in a private subnet. The worker nodes are deployed in private subnets and joined to the control plane using the private IP address of the nodes.

For example, in the us-west-2 region cluster deployed in us-west-2a, us-west-2b, and us-west-2c availability zones:

  • Control plane: One node group per availability zone (us-west-2a, us-west-2b, us-west-2c)
  • Worker nodes: One node group spanning all availability zones
NAME				        ROLE		    MACHINETYPE	MIN	MAX	SUBNETS
control-plane-foo-cluster-0	ControlPlane	t3.medium	1	1	us-west-2a
control-plane-foo-cluster-1	ControlPlane	t3.medium	1	1	us-west-2b
control-plane-foo-cluster-2	ControlPlane	t3.medium	1	1	us-west-2c
worker-test-mg-ng-0		    Node		    t3.medium	1	1	us-west-2a,us-west-2b,us-west-2c

GCP Vanilla K8s Cluster Deployment (Self-Managed)​

TBD