Skip to content
Home » EKS INTALLATION AND DEPLOYMENT OF APPLICATION WITH INGRESS CONTROLLER

EKS INTALLATION AND DEPLOYMENT OF APPLICATION WITH INGRESS CONTROLLER

DESCRIPTION OF PROJECT STRUCTURE, (AMAZON ELASTIC KUBERNETES SERVICE)

AWS EKS makes it easy to run Kubernetes on AWS without installing or managing your own Kubernetes control plane. In this article, we’ll explore the key features and benefits of using EKS for container orchestration.                                                                                                                                                                

Key features of EKS include:

    • Fully managed Kubernetes control plane — AWS handles provisioning and managing the Kubernetes control plane consisting of the API server, etcd, controller manager, and other components.
    • High availability — The Kubernetes control plane runs across multiple Availability Zones to ensure high availability.
    • Serverless Kubernetes masters — You don’t need to provision EC2 instances for the Kubernetes control plane. It’s serverless and managed by AWS.
    • Integrated with other AWS services — EKS integrates natively with services like IAM, VPC, ELB, EBS, and CloudTrail for easier operation and monitoring.

 Alternative approach for eks for running kubernetes in the cloud

1. You can carry out the infrastructure in aws without eks  by spinning up 6 instances 3 for master nodes 3 for worker nodes and then you install the configuration in the following nodes. Before a user is able to access application they talk to the control plane before the data plane.     Master nodes have api server, etcd, scheduler,  controller  all in the control plane In data-plane plane we install container, container network interface, container runtime, dns service, kube proxy

Structure of the project

  1. Creation of clusters on the eks worker nodes and master nodes
  2. Allowing users to accesses the application
  3. Pod is created in the worker node
  4. Services will be created to expose the pod to the outside world
  5. Usually the entire cluster and pod will be inside a vpc which has the public and private subnets. However applications are normally deployed in the private subnet.
  6. Loadbalancer mode provides a public ip address to which users can access the application which is very expensive.
  7. Best approach is ingress

Ingress controllers

Initial setup of your project at the windows command line after creating your project folder and navigating into it.

Navigate to your ec2 account and successfully create a Vpc account.

We have to make sure that subnets should be created within the virtual private cloud as seen in the Architecture.

Subnets have been created within the virtual private cloud

Some subnets were already available within the vpc before creating additional subnets. Nb: These were automatically created when an Ec2 instance was initiated

Subnets have officially been created.