write Kubernetes app configurations, with a strong ops/sysadmin background in runnings apps in production

I am searching for a talent that can write Kubernetes app configurations, with a strong ops/sysadmin background in runnings apps in production I already have the Kubernetes cluster working. What i need is a prototype / proof of concept / skeleton of deployment code for LAMP stacks to deploy on a Kubernetes cluster, following the constraints and requirements below To put my request into context, i am an experienced Linux sysadmin getting started on Kubernetes (mostly theory and books until now) and i would need a headstart from an experienced Kubernetes admin. And also make sure i get the right choices and suggestions for a production and a good and clean code base to iterate on. __(see other comments in the full document attached)__ __(see all requirements and deliverables in the full document attached)__ === 1st deliverable (as soon as possible) YAML files to create some app LAMP stacks (any LAMP app such as Wordpress, it does not matter at this stage). the App would be a collection of pods for: * Apache * PHP-FPM * Mysql * sometimes Elasticsearch * PHP Cron job * volumes for Mysql, ES, PHP (containing both app and data). Apache, PHP-FPM and the PHP Cron job need read+write access on the same files (should they mount the same volume, or access each a synchronized replica) ? If possible use public stock images to which customization is applied at init or config, rather than building and distributing a custom image Each app is not distributed or does not need to autoscale. Only 1 PHP container, 1 Mysql and sometimes 1 ElasticSearch per app. Neither of these components need to be HA, but each requires a persistent storage that should be either synced or replicated to some other node, so that Kubernetes can reschedule on another node and app service is restored with minimal downtime with no data loss (DFS volumes such as Longhorn or OpenEBS ? Or a NFS pod running on some DFS or even a ZFS asynchronously replicated storage ? Or another suggestion or solution ?) Please keep code and YAML configurations reasonably simple and commented, especially comments about why certain choice is made for example __(see all requirements and deliverables in the full document attached)__