What is Amazon EKS?
Amazon Elastic Kubernetes Service is a fully managed service of kubernetes, you can also call it kubernetes as a service. EKS is the best place to run Kubernetes for several reasons.
- You can choose to run your EKS clusters using AWS Fargate, which is serverless compute for containers. Fargate removes the need to provision and manage servers, lets you specify and pay for resources per application, and improves security through application isolation by design.
- EKS is deeply integrated with services such as Amazon Auto Scaling Groups, AWS Identity and Access Management (IAM), CloudWatch, Amazon Virtual Private Cloud (VPC), etc. providing you a seamless experience to monitor, scale, and load-balance your applications.EKS gives Serverless Option (Farget), Security and built with the community.
- EKS provides a scalable and highly-available control plane that runs across multiple availability zones to eliminate a single point of failure.
What is Docker?
Docker is a containerization tool. Using Docker we can launch the entire environment for our application server just in 1 second. Docker run in a isolation world so it is very secure to deploy our application on top of docker container.
What is Kuberntes?
Kubernetes is a management (orchestration) tool of container. Kubernetes doesn’t launch the container, it ask/contact the docker/podman/cri-o behind the scene to launch the container if requirement comes. Kubernetes is meant for only one thing to manage the container. Here in EKS in these practical we are using docker to launch our application on docker container.
What is Joomla?
Joomla is a free and open source content management system (CMS) for publishing web content, developed by Open Source Matters, Inc. It is built on a model view controller web application framework that can be used independently of the CMS. Joomla is written in PHP, uses object oriented programming techniques (since version 1.5) and software design patterns, stores data in a MYSQL, MSSQL (since version 2.5), or PostgrsSQL (since version 3.0) database. In this practical I have used MYSQL database.
Prerequisites:
- AWS CLI : Use to manage the aws services.
- Kubectl: Use for communication with master cluster API server.
- Eksctl: Use to create and manage entire kubernetes cluster on aws eks.
Steps to be followed are:
AWS Identity and Access Management (IAM) is a web service that helps you securely control access to AWS resources. You use IAM to control who is authenticated (signed in) and authorized (has permissions) to use resources.
When you first create an AWS account, you begin with a single sign-in identity that has complete access to all AWS services and resources in the account. This identity is called the AWS account root user and is accessed by signing in with the email address and password that you used to create the account.
In this task we have to use admin account to give full power once it is done you will get access key and secret key note it done which is used to login to aws using aws cli
Command to login in AWS account:
Now give the access key and secret key which you noted down
So to create EKS Cluster we have to first install EKSCTL and set the path. To create EKS cluster from CLI we need to write a YAML file (Manifest file) which contain all details as what we need.
https://github.com/sahanabalappa/AWS-EKS/blob/master/create_cluster.yml
Using this command we create a EKS Cluster.
When we update the .kube config file then only kubectl get the access to go in eks cluster. In these config file complete eks cluster information and access is mentioned. Without these kubectl command can’t go inside the eks cluster and launch the POD in slave node.
Command to update the config file of kubernetes:
In AWS EFS, aws create a EFS server in all 3 data center because of disaster management. It give high availability, elasticity, scalability and all EBS and S3 limitation can be solve by EFS. For this task I am using EFS (Elastic File System) for persistent storage. After NFS server created we have to do some changes in YAML file of efs provisioner(Add system_id and NFS server in efs provisioner file) and then we have to install a package call amazon-efs-utils in every worker nodes/instances.
In this step run all these YAML file using kustomization. https://github.com/sahanabalappa/AWS-EKS/blob/master/kustomization.yml
Run this command to run kustomization yaml file:
After following this steps Joomla successfully deployed. All data of Joomla and MYSQL Database is storing in EFS, If any POD fail client won’t face any downtime.