|
1 |
| -Creating Kubernetes cluster on the AWS CLOUD--> Service name--> EKS |
| 1 | +## Creating Kubernetes cluster on the AWS CLOUD |
| 2 | +### Service name: EKS |
2 | 3 |
|
3 | 4 | Below are the steps to create the EKS Cluster.
|
4 | 5 |
|
5 |
| -1] Create the VPC. |
6 |
| - |
7 |
| -2] Create IAM role for EKS Cluster: |
8 |
| - IAM --> Role --> EKS --> ROLE-NAME |
9 |
| - |
10 |
| -3] Create the EKS Cluster on AWS Dashboard (While creating it, attach the role created in second steps.) |
11 |
| - |
12 |
| -4] Access EKS cluster from your machine |
13 |
| - - install kubectl, aws cli, |
14 |
| - - configure aws cli(aws configure,) |
15 |
| - |
16 |
| - |
17 |
| -<!-- |
18 |
| -aws configure --profile PROFILE-NAME |
19 |
| -aws configure list-profiles |
20 |
| -export AWS_PROFILE=PROFILE-NAME |
21 |
| -aws sts get-caller-identity |
22 |
| -aws eks describe-cluster --name CLUSTER-NAME --region us-east-2 |
23 |
| -aws eks update-kubeconfig --region us-east-2 --name CLUSTER-NAME |
24 |
| -kubectl get nodes |
25 |
| -kubect get pods |
26 |
| ---> |
27 |
| - |
28 |
| -5] Create the New IAM role for workernodegroup: |
29 |
| - |
30 |
| - IAM --> Role --> EKS --> AmazonEKS_CNI_Policy --> AmazonEKSWorkerNodePolicy --> AmazonEC2ContainerRegistryReadOnly --> ROLE-NAME |
31 |
| - |
32 |
| -6] Create the EKS workernodegroup on AWS Dashboard (While creating it, attach the role created in 5th steps.) |
33 |
| - |
34 |
| -7] Once workernodegrp ready u r good to go to deploy application on it... |
35 |
| - |
| 6 | +1. Create the VPC. |
| 7 | + |
| 8 | +2. Create IAM role for EKS Cluster: |
| 9 | + - Go to IAM > Role > EKS > ROLE-NAME |
| 10 | + |
| 11 | +3. Create the EKS Cluster on AWS Dashboard: |
| 12 | + - Attach the role created in the previous step while creating the cluster. |
| 13 | + |
| 14 | +4. Access EKS cluster from your machine: |
| 15 | + - Install kubectl and aws cli. |
| 16 | + - Configure aws cli using the command: `aws configure`. |
| 17 | + - Run the following commands: |
| 18 | + |
| 19 | + ```bash |
| 20 | + aws configure --profile PROFILE-NAME |
| 21 | + aws configure list-profiles |
| 22 | + export AWS_PROFILE=PROFILE-NAME |
| 23 | + aws sts get-caller-identity |
| 24 | + aws eks describe-cluster --name CLUSTER-NAME --region us-east-2 |
| 25 | + aws eks update-kubeconfig --region us-east-2 --name CLUSTER-NAME |
| 26 | + kubectl get nodes |
| 27 | + kubectl get pods |
| 28 | + |
| 29 | +5. Create a new IAM role for workernodegroup: |
| 30 | + Go to IAM > Role > EKS > AmazonEKS_CNI_Policy > |
| 31 | + AmazonEKSWorkerNodePolicy > AmazonEC2ContainerRegistryReadOnly > ROLE-NAME |
| 32 | + |
| 33 | +7. Create the EKS workernodegroup on AWS Dashboard: |
| 34 | + Attach the role created in the previous step while creating the workernodegroup. |
| 35 | + Once the workernodegroup is ready, you are good to go to deploy applications on it |
0 commit comments