Using EKS in order to deploy SQL & WordPress

Introduction to EKS -
EKS stands for Amazon Elastic Kubernetes Service, which is a fully-managed Kubernetes service. Which can be used in order to do Hybrid Deployment, Machine Learning

Why Use EKSCTL? -
eksctl automatically creates several AWS resources for you. If you’d rather manually create most of the resources and better understand how they interact with each other, then use the AWS Management Console to create your cluster and worker nodes.

How does it work?
eksctl creates a cloud formation, which is a stack of operations to be performed. Which in turn creates the whole infrastructure. (i.e. ec2 instances, security groups, etc).

Steps-
1. Creating a role using IAM, with administrative permission, and login in AWS CLI using AWS configure command.

Login in CLI

2. Creating a cluster using eksctl command in CLI with a .yml which contains the configuration of the cluster.

.yml file for cluster creation

Run the above using the code

eksctl create cluster -f cluster.yml

3. Running the above code using eksctl creates the cluster, which takes apx 20 mins to create. The same can be verified by checking the EKS service section in the AWS Console.

While Creation

4. Configuring the config files of the cluster using

aws eks update-kubeconfig --name cluster11

5. Following this, we need to add amazon-efs-utils in the node by logging inside the instance using ssh, and the key pair.

6. Create an EFS with public subnets, and the respective security groups.

7. Create a namespace

kubectl create ns task

8. Create an EFS provisioner, using the ID and DNS from the EFS system.

kind: Deployment
apiVersion: apps/v1
metadata:
name: efs-provisioner
spec:
selector:
matchLabels:
app: efs-provisioner
replicas: 1
strategy:
type: Recreate
template:
metadata:
labels:
app: efs-provisioner
spec:
containers:
- name: efs-provisioner
image: quay.io/external_storage/efs-provisioner:v0.1.0
env:
- name: FILE_SYSTEM_ID
value: fs-ae26ac7f
- name: AWS_REGION
value: ap-south-1
- name: PROVISIONER_NAME
value: lw-course/aws-efs
volumeMounts:
- name: pv-volume
mountPath: /persistentvolumes
volumes:
- name: pv-volume
nfs:
server: fs-ae26ac7f.efs.ap-south-1.amazonaws.com
path: /

the command to run the following file -

kubectl create -f deploy.yml -n task

9. Create a YML code to modify some permissions using ROLE BASED ACCESS CONTROL (RBAC)-

apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
name: nfs-provisioner-role-binding
subjects:
- kind: ServiceAccount
name: default
namespace: task
roleRef:
kind: ClusterRole
name: cluster11
apiGroup: rbac.authorization.k8s.io

the command to run the following file -

kubectl create -f rolechange.yml -n task

10. Create a Storage Class which will create a PVC as well as a dynamic PV. I have created two PVCs of 10 Gib each. The size can be altered according to usage.

kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: aws-efs
provisioner: lw-cluster/aws-efs
 — -
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: efs-wordpress
annotations:
volume.beta.kubernetes.io/storage-class: “aws-efs”
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: 10Gi
 — -
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: efs-mysql
annotations:
volume.beta.kubernetes.io/storage-class: “aws-efs”
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: 10Gi

the command to run the following file -

kubectl create -f storageclass.yml -n task

11. Create a secret for the password for MySQL password -

kubectl create secret generic mysql-pass — from-literal=password=redhat -n task

12. launch an MYSQL which will be connected to WordPress. For this purpose, I have used MYSQL version 5.6. This can also be altered.

apiVersion: v1
kind: Service
metadata:
name: wordpress-mysql
labels:
app: wordpress
spec:
ports:
- port: 3306
selector:
app: wordpress
tier: mysql
clusterIP: None
 — -
apiVersion: apps/v1 # for versions before 1.9.0 use apps/v1beta2
kind: Deployment
metadata:
name: wordpress-mysql
labels:
app: wordpress
spec:
selector:
matchLabels:
app: wordpress
tier: mysql
strategy:
type: Recreate
template:
metadata:
labels:
app: wordpress
tier: mysql
spec:
containers:
- image: mysql:5.6
name: mysql
env:
- name: MYSQL_ROOT_PASSWORD
valueFrom:
secretKeyRef:
name: mysql-pass
key: password
ports:
- containerPort: 3306
name: mysql
volumeMounts:
- name: mysql-persistent-storage
mountPath: /var/lib/mysql
volumes:
- name: mysql-persistent-storage
persistentVolumeClaim:
claimName: efs-mysql

the command to run the following file -

kubectl create -f sqldeploy.yml -n task

13. Now launch WordPress & connect to SQL

http://13.126.41.98/2020/07/14/eks-task/

14. This was all about the Task of Creating a Kubernetes cluster and using WordPress in the same.