AWS EKS TRANING BY VIMAL DAGA SIR .
What is aws eks?
Amazon Elastic Kubernetes Service (Amazon EKS) is a fully managed Kubernetes service. Customers such as Intel, Snap, Intuit, GoDaddy, and Autodesk trust EKS to run their most sensitive and mission critical applications because of its security, reliability, and scalability.
EKS is the best place to run Kubernetes for several reasons. First, 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. Second, EKS is deeply integrated with services such as Amazon CloudWatch, Auto Scaling Groups, AWS Identity and Access Management (IAM), and Amazon Virtual Private Cloud (VPC), providing you a seamless experience to monitor, scale, and load-balance your applications. Third, EKS integrates with AWS App Mesh and provides a Kubernetes native experience to consume service mesh features and bring rich observability, traffic controls and security features to applications. Additionally, EKS provides a scalable and highly-available control plane that runs across multiple availability zones to eliminate a single point of failure.
Launching of cluster from yaml code on eks.
eksctl create cluster -f cluster.yml
We have also to create a namespace for the cluster and setup the kubectl it is used by admin to control the cluster this is a powerful command (kubectl).
for launching pods inside the cluster we use the command. “kubectl create deployment myweb — image= (image name we used from docker)
UPDATION OF KUBECONFIG FILE AFTER CREATING THE EBS VOLUME AND MOUNTING IT TO IT.
kubectl get nodes , kubectl get pods ,kubectl cluster info,kubectl get pods -o wide ,kubectl conifg views (various command used ).The below image shows the structure of pvc and storage class creation.
EFS SETUP
Amazon Elastic File System (Amazon EFS) provides a simple, scalable, fully managed elastic NFS file system for use with AWS Cloud services and on-premises resources. It is built to scale on demand to petabytes without disrupting applications, growing and shrinking automatically as you add and remove files, eliminating the need to provision and manage capacity to accommodate growth.
Amazon EFS offers two storage classes: the Standard storage class, and the Infrequent Access storage class (EFS IA). EFS IA provides price/performance that’s cost-optimized for files not accessed every day. By simply enabling EFS Lifecycle Management on your file system, files not accessed according to the lifecycle policy you choose will be automatically and transparently moved into EFS IA. The EFS IA storage class costs only $0.025/GB-month*.
While workload patterns vary, customers typically find that 80% of files are infrequently accessed (and suitable for EFS IA), and 20% are actively used (suitable for EFS Standard), resulting in an effective storage cost as low as $0.08/GB-month*. Amazon EFS transparently serves files from both storage classes in a common file system namespace.
Amazon EFS is designed to provide massively parallel shared access to thousands of Amazon EC2 instances, enabling your applications to achieve high levels of aggregate throughput and IOPS with consistent low latencies.
Amazon EFS is well suited to support a broad spectrum of use cases from home directories to business-critical applications. Customers can use EFS to lift-and-shift existing enterprise applications to the AWS Cloud. Other use cases include: big data analytics, web serving and content management, application development and testing, media and entertainment workflows, database backups, and container storage.
Amazon EFS is a regional service storing data within and across multiple Availability Zones (AZs) for high availability and durability. Amazon EC2 instances can access your file system across AZs, regions, and VPCs, while on-premises servers can access using AWS Direct Connect or AWS VPN.
LAUNCHING OF JOOMLA ON CLUSTER AND IT IS CONNECTED TO THE MYSQL DATABASE.
ALL THE RESOURCES ARE DESTROYED FINALLY.
ALL THE RESOURCES CAN BE MONITORED BY GRAFANA AND PROMETHESIS.
github link-https://github.com/shrey285001
Traning by -https://www.linkedin.com/in/vimaldaga/
Blog written by -https://www.linkedin.com/in/shrey-gupta-930a59169/
