Step by step tutorial for those who have zero knowledge to Amazon EKS.
-
The project here is for demonstration purpose only.
-
DO NOT blindly apply it to your production environments.
- eksctl - The official CLI for Amazon EKS
- kubectl - The Kubernetes command-line tool
- helm - The Kubernetes Package Manage
- Your AWS Profile have proper permission configured.
- All the tools required were setup properly
- All the resources are under
us-east-1 - The cluster name would be
eks-auto-mode
- Goal 1: Create EKS Cluster with
eksctl - Goal 2: Deploy workload and make sure Auto Mode work as expeceted
- Goal 3: Figure out why HPA and Ingress not working?
- Goal 4: Fix the issues
- Goal 5: Figure out why
kubectl scale ...would failed - Goal 6: Try to turn ALB entry from HTTP to HTTPS
- Goal 7: How to switch to Network Load Balancer (NLB)?
- Goal 8: Cleanup
Make sure you have latest eksctl installed and you should be able to create EKS cluster with minimal setup as follow.
% eksctl create cluster -f ./cluster-config/cluster-auto.yamlOR (only when accessEntries not empty)
% cat cluster-config/cluster-auto.yaml | \ AWS_ACCOUNT_ID=$(aws sts get-caller-identity --output json --query "Account" | sed 's/"//g') envsubst '${AWS_ACCOUNT_ID}' | \ TARGET_ROLE_NAME=DemoRole envsubst '${TARGET_ROLE_NAME}' | eksctl create cluster -f -Verify there have no EKS node running initially.
% kubectl get nodes No resources found # expected, since we are running Auto Mode enabled cluster.NOTE For eksctl version higher than v0.201.0, you should find there have 1 node created, since metrics-server became default addon for eksctl created cluster.
At this stage, you would need to have kubectl installed. Then you should be able to create Deployment, HPA, Service and Ingress resources.
% kubectl apply -f ./examples/simple/ deployment.apps/nginx-deployment created horizontalpodautoscaler.autoscaling/nginx-hpa created ingress.networking.k8s.io/nginx-ingress created service/nginx-service createdAfter workload deployed, there should have node provisioned by Auto Node after few seconds wait.
% kubectl get nodes -L "eks.amazonaws.com/compute-type" NAME STATUS ROLES AGE VERSION COMPUTE-TYPE i-EXAMPLE1234567890 Ready <none> 11s v1.34.x-eks-1234567 auto% kubectl get pods,deployments,hpa,service,ingress NAME READY STATUS RESTARTS AGE pod/nginx-deployment-54697596c9-7bc4f 1/1 Running 0 22s pod/nginx-deployment-54697596c9-gqpv5 1/1 Running 0 22s NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/nginx-deployment 2/2 2 2 22s NAME REFERENCE TARGETS MINPODS MAXPODS REPLICAS AGE horizontalpodautoscaler.autoscaling/nginx-hpa Deployment/nginx-deployment cpu: <unknown>/80% 2 10 2 22s # <-------- why no metrics? NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/kubernetes ClusterIP 10.100.0.1 <none> 443/TCP 12m service/nginx-service NodePort 10.100.137.151 <none> 80:30928/TCP 21s NAME CLASS HOSTS ADDRESS PORTS AGE ingress.networking.k8s.io/nginx-ingress alb entry1.example.com 80 22s # <-------- no address shown, why?After fixing the issue, you should be able to see command output as follow,
% kubectl get ingress nginx-ingress NAME CLASS HOSTS ADDRESS PORTS AGE nginx-ingress alb entry1.example.com k8s-default-XXX.REGION.elb.amazonaws.com 80 60sAfter fixing HPA issue, you should be able to see command output as follow,
% kubectl get hpa nginx-hpa NAME REFERENCE TARGETS MINPODS MAXPODS REPLICAS AGE nginx-hpa Deployment/nginx-deployment 2%/80% 2 10 2 2m7s% kubectl scale --replicas 12 deployment nginx-deployment deployment.apps/nginx-deployment scaledWhy the Pod count not able to reach desired pod count 12 but quickly scale down back to 2... why is that ?
Service with HTTP is clearly unsafe, how to made it safe with HTTPS?
If you solve can provision ALB then you should be able to create NLB as well. But how...? 🤔
Terminate all resources that we created earlier.
% kubectl delete -f ./examples/simple/ --ignore-not-foundTerminate the EKS cluster
% eksctl delete cluster -f ./cluster-config/cluster-auto.yamlOPTIONAL Cleanup IAM User/Role/Policy and Identity Provider (IdP) with care.
There's another repository with common used addons installation scripts: