DevOps - Kubernetes Manifest for WordPress Stack Deployment
- or -
Post a project like this3
£100(approx. $125)
- Posted:
- Proposals: 16
- Remote
- #4189004
- Open for Proposals
1550+ Projects (iOS | Android | Mac OS | Web | Win | BlockChain | IOT)
Bad Vilbel
Web and App Development | Database Expert | Database Analysis| Python Developer
Islamabad
51549661379563784896857017506952499006650462965239697911027100595051021796910753489
Description
Experience Level: Entry
I am looking for someone who has experience in DevOps especially in Kubernetes and Docker to Create a Kubernetes Manifest using Kustomize or similar to:
1. Deploy MariaDB 8.x (Latest) - Persistent Volume
2. Deploy WordPress on NGINX Webserver and PHP FPM 8.3 (Latest) - Persistent Volume
3. Deploy Varnish Cache configured for WordPress Site
4. Deploy Matomo Analytics
Current Infrastructure: Kubernetes Running on Digital Ocean with NGINX Ingress Controller and Certmanager using Lets Encrypt.
The flow should be:
1. Traffic to https://mydomain.com will hit the Digital Loadbalancer then to the k8s cluster via the Ingress controller.
2. The first point of entry to the stack should be the Varnish Cache pod
3. WordPress pod will be behind Varnish Cache communication through internal service
4. Matomo Analytics pod will be there independently on a separate subdomain ingress (matomo.mydomain.com) which will eventually track the WP Website
5. MariaDB Pod will be there serving all the services that need DB in the stack through separate databases within through internal service.
Things to consider:
1. The solution should be fully tested and documented.
2. If any custom image is created (e.g. Wordpress with NGINX) it needs to be scripted so the image can be reproduced using docker file etc. as and when needed
3. The Digital Ocean Load Balancer and Ingress controller has proxy protocol enabled, Varnish Cache must be configured such a way that the internal WordPress installation is able to detect the remote IP address
4. Varnish Cache configuration must be adjustable during deployment. So if any change is needed it should be done to the Varnish pod by redeploying it with the desired configuration.
1. Deploy MariaDB 8.x (Latest) - Persistent Volume
2. Deploy WordPress on NGINX Webserver and PHP FPM 8.3 (Latest) - Persistent Volume
3. Deploy Varnish Cache configured for WordPress Site
4. Deploy Matomo Analytics
Current Infrastructure: Kubernetes Running on Digital Ocean with NGINX Ingress Controller and Certmanager using Lets Encrypt.
The flow should be:
1. Traffic to https://mydomain.com will hit the Digital Loadbalancer then to the k8s cluster via the Ingress controller.
2. The first point of entry to the stack should be the Varnish Cache pod
3. WordPress pod will be behind Varnish Cache communication through internal service
4. Matomo Analytics pod will be there independently on a separate subdomain ingress (matomo.mydomain.com) which will eventually track the WP Website
5. MariaDB Pod will be there serving all the services that need DB in the stack through separate databases within through internal service.
Things to consider:
1. The solution should be fully tested and documented.
2. If any custom image is created (e.g. Wordpress with NGINX) it needs to be scripted so the image can be reproduced using docker file etc. as and when needed
3. The Digital Ocean Load Balancer and Ingress controller has proxy protocol enabled, Varnish Cache must be configured such a way that the internal WordPress installation is able to detect the remote IP address
4. Varnish Cache configuration must be adjustable during deployment. So if any change is needed it should be done to the Varnish pod by redeploying it with the desired configuration.
Sakib A.
100% (11)Projects Completed
11
Freelancers worked with
9
Projects awarded
35%
Last project
23 Dec 2020
United Kingdom
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies