Deployment of WordPress on Amazon EKS without utilizing Amazon EFS (Elastic File System)

Overview

WordPress deployment on Amazon EKS without Amazon EFS necessitates new storage and resource management strategies. This review will look at alternative options, Kubernetes-native functionality, and optimization tactics for a scalable and cost-effective deployment on Amazon EKS.

Introduction

In cloud-native application deployment, orchestrating WordPress on Amazon Elastic Kubernetes Service (EKS) is a strategic choice for organizations seeking flexibility, scalability, and reliability. While Amazon EFS serves as a conventional storage solution for EKS environments, there are instances where alternative methods offer distinct advantages. This introduction sets the stage for exploring optimized deployment strategies for WordPress on Amazon EKS, emphasizing the avoidance of Amazon EFS dependency and adopting innovative storage and resource management approaches.

Step-by-step Guide

Helm, a package manager for Kubernetes, may be used to deploy WordPress on Amazon EKS without utilizing Amazon EFS. The steps are here:

1. At first, AWS CLI, EKSCTL, and HELM should be installed and configured on the machine.
2. EKS cluster provisioning:Make a YAML file to configure the cluster. I have named it “my-eks-cluster”.apiVersion: eksctl.io/v1alpha5kind: ClusterConfigmetadata:

   name: my-eks-cluster

   region: ap-south-1

   managedNodeGroups:

   – name: newdev-ng-1

   instanceType: t3.large

   minSize: 1

   maxSize: 1

   desiredCapacity: 1

   volumeSize: 20

   volumeEncrypted: true

   volumeType: gp3

   ssh:

   allow: true

   publicKeyName: eks

   tags:

   Env: Dev

   iam:

   attachPolicyARNs:

   – arn:aws:iam::aws:policy/AmazonEKSWorkerNodePolicy

   – arn:aws:iam::aws:policy/AmazonEKS_CNI_Policy

   – arn:aws:iam::aws:policy/ElasticLoadBalancingFullAccess

   3. Create a cluster by running this command.

   eksctl create cluster -f demo-eks-cluster.yaml

   1	eksctl create cluster -f demo-eks-cluster.yaml

   4. To confirm the provisioning of nodes, run

   kubectl get nodes

   1	kubectl get nodes

   

   5. Deploy WordPress on EKS:Add helm repo to the environment.

   helm repo add my-new-repo https://charts.bitnami.com/bitnami

   1	helm repo add my-new-repo https://charts.bitnami.com/bitnami

   6. Then, install the helm chart for WordPress.

   helm install new-release my-new-repo/wordpress --set wordpressPassword=password

   1	helm install new-release my-new-repo/wordpress --set wordpressPassword=password

   7. After successful deployment, check the pods and see if the status reads “Running”

   kubectl get pods

   1	kubectl get pods

   
   

   8. Accessing the WordPress website

   export SERVICE_IP=$(kubectl get svc --namespace default new-release-wordpress --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")

   1	export SERVICE_IP=$(kubectl get svc --namespace default new-release-wordpress --template "{{ range (index .status.loadBalancer.ingress 0) }}{{ . }}{{ end }}")

   

   echo "WordPress URL: http://$SERVICE_IP/"

   1	echo "WordPress URL: http://$SERVICE_IP/"

   

   

   echo "WordPress Admin URL: http://$SERVICE_IP/admin"

   1	echo "WordPress Admin URL: http://$SERVICE_IP/admin"

   

   

   9. Clean up

   eksctl delete cluster my-eks-cluster

   1	eksctl delete cluster my-eks-cluster

   

About CloudThat