Why should you care?

AwsVerse platform team hosts 30 microservices on shared EKS with tenant namespaces.

See it live — copy this example

Run in AWS CloudShell / local AWS CLI v2, or follow the matching steps in the AWS Console (Free Tier).

eksctl create cluster -f - <<EOF
apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig
metadata:
  name: awsverse-platform
  region: ap-south-1
managedNodeGroups:
  - name: ng-1
    instanceType: t3.medium
    minSize: 2
    maxSize: 6
EOF
kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/main/docs/install/iam_policy.json

What happened?

• eksctl creates EKS with managed nodes; LB controller manifest wires Ingress to ALB.
• IRSA roles scoped per Deployment service account.

Practice next

1. Create EKS cluster with eksctl.
2. Install LB controller and metrics-server.
3. Deploy sample Ingress; verify ALB provisioned.
4. Add Fargate profile for kube-system isolation.
5. Enable control plane audit logs.

Remember

EKS platform with IRSA isolation. ALB Ingress for north-south traffic. Cluster autoscaler for node scale.

AwsVerse k8s fleet

Platform supports 8 product teams.

Outcome: Shared EKS cuts cluster ops overhead 60% vs per-team clusters.