{"id":40020,"date":"2016-09-01T11:26:36","date_gmt":"2016-09-01T05:56:36","guid":{"rendered":"https:\/\/2thenew.today\/blog\/?p=40020"},"modified":"2024-01-02T17:46:15","modified_gmt":"2024-01-02T12:16:15","slug":"setup-and-configure-kubernetes-minions-in-multiple-azs-on-aws","status":"publish","type":"post","link":"https:\/\/2thenew.today\/blog\/setup-and-configure-kubernetes-minions-in-multiple-azs-on-aws\/","title":{"rendered":"Setup and Configure Kubernetes Minions in Multiple AZs on AWS"},"content":{"rendered":"

\"Image<\/p>\n

In today’s blog, I will be explaining how to set up Kubernetes Minion nodes in multiple availability zones on AWS. Please refer this blog <\/a>if you are new to setting up a cluster on AWS EC2. It uses a kube_up script to bring the cluster up on single Availability Zone (AZ). If that zone goes down due to some reasons, your entire applications will be down, so we need to build the solution on multiple AZs.<\/p>\n

Kubernetes tagged the tag “KubernetesCluster” to the all of the AWS resources<\/a>. The value of the tag say “test-kubernetes-aws” has been provided while setting up the cluster on single AZ in the config-default.sh file on INSTANCE_PREFIX variable:<\/p>\n

[shell]
\nINSTANCE_PREFIX="${KUBE_AWS_INSTANCE_PREFIX:-test-kubernetes-aws}"
\n[\/shell]<\/p>\n

Below are steps to setup minion nodes on multiple AZs:<\/strong><\/p>\n

1)\u00a0Update the Autoscaling group (ASG) of the minion nodes to add one more subnet<\/p>\n

Initial setup has single subnet:<\/em>
\n\"asgold\"<\/p>\n

Add one more subnet to the ASG:<\/em>
\n\"ASG\"<\/p>\n

2) Add tag “KubernetesCluster” to the newly added Subnet:
\n\"subnet\"<\/p>\n

3) Associate new subnet to the existing route table.<\/p>\n

Initial setup has only one subnet attached to the route table:<\/em>
\n\"route1\"<\/p>\n

Associate new subnet to the route table:<\/em>
\n\"subnets\"<\/p>\n

4) Make sure that route table has the “KuberntesCluster” tag:
\n\"routetag\"<\/p>\n

Once the above steps have been completed, update the desired capacity of the ASG of minions to add one more minion node. New Minion gets created in the new subnet ‘us-east-1d’.
\n<\/strong><\/p>\n

Let’s test the above configuration and make sure that new minion node is ready to serve traffic:<\/strong><\/p>\n

1) Create the pod and service my-nginx using the following the YAML:<\/p>\n

[code]
\napiVersion: extensions\/v1beta1
\nkind: Deployment
\nmetadata:
\nname: my-nginx
\nspec:
\nreplicas: 1
\ntemplate:
\nmetadata:
\nlabels:
\nrun: my-nginx
\nspec:
\ncontainers:
\n– name: my-nginx
\nimage: nginx
\nports:
\n– containerPort: 80
\n—
\napiVersion: v1
\nkind: Service
\nmetadata:
\nname: my-nginx
\nspec:
\nports:
\n– name: "www"
\nport: 80
\ntargetPort: 80
\nselector:
\nrun: my-nginx
\ntype: LoadBalancer
\n[\/code]<\/p>\n

In the above code, I am using service type:LoadBalancer, this will create an ELB, which is an endpoint for a service. The following command will create the pod and service:<\/p>\n

[shell] kubectl apply -f nginx.yaml [\/shell]<\/p>\n

3) To check on which Minion node a pod has been created, use the following command:<\/p>\n

[shell] kubectl get pods -o wide [\/shell]<\/p>\n

P.S<\/strong>: Kubernetes can assign pods to any of the nodes in the cluster. In my case it has assigned the pod to the instance in new subnet (‘us-east-1d’):
\n\"pods\"<\/p>\n

2)\u00a0 Check ELB; it should have instances on both AZs us-east-1d, us-east-1c and in service state:
\n\"elb\"<\/p>\n

3) Hit the ELB DNS (endpoint of the service) on the browser and you will see the Nginx welcome page:
\n\"nginx\"<\/p>\n

Hope it helps in setting up minion nodes on multi AZs. In the upcoming blog, I will be explaining how to set up master on Multiple AZs( HA Kubernetes cluster).<\/p>\n","protected":false},"excerpt":{"rendered":"

In today’s blog, I will be explaining how to set up Kubernetes Minion nodes in multiple availability zones on AWS. Please refer this blog if you are new to setting up a cluster on AWS EC2. It uses a kube_up script to bring the cluster up on single Availability Zone (AZ). If that zone goes […]<\/p>\n","protected":false},"author":970,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":7,"footnotes":""},"categories":[1174,2348,1],"tags":[2366,1547,1746,3987,3989,3986,3965,3984,3988,3990,3972,3985,3991],"class_list":["post-40020","post","type-post","status-publish","format-standard","hentry","category-aws-2","category-devops-technology","category-technology","tag-aws-devops","tag-aws-ec2","tag-aws-elb","tag-aws-multi-az","tag-cross-zone-minion-nodes","tag-ha-kubernetes-cluster","tag-kubernetes","tag-kubernetes-cluster","tag-kubernetes-kube_up","tag-kubernetes-pods","tag-kubernetes-service","tag-master-minions","tag-setup-cross-zone-minions-on-aws"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t