Fill out the secrets file in deploy/kubernetes/secrets/secrets.yaml
Fill out the ingress deploy/kubernetes/manifests/ingress.yaml because I own wrestlingdev.com not you. Put your own domain in there.
Run kubectl apply -f deploy/kubernetes/secrets/
Run kubectl apply -f deploy/kubernetes/manifests/

What do I get?

Wrestlingdev deployed with 2 replicas. Autoscaling is turned on up to 4 replcias.
A standalone mariadb.
A standalone memcahced.
A single job runner to run wrestlingdev background jobs.

How do I update the app?

Each push to master updates the docker prod tag and also pushes a tag with the git hash.

Set the git hash as a variable TAG=$(git rev-parse --verify HEAD)
Update the wrestlingdev deployment tag kubectl --record deployment.apps/wrestlingdev-app-deployment set image deployment.v1.apps/wrestlingdev-app-deployment wrestlingdev-app=jcwimer/wrestlingdev:${TAG}
Update the wrestlingdev job runner tag kubectl --record deployment.apps/wrestlingdev-worker-deployment set image deployment.v1.apps/wrestlingdev-worker-deployment wrestlingdev-worker=jcwimer/wrestlingdev:${TAG}
Delete the db migrations job so you can re-run it kubectl delete job wrestlingdev-db-create-migrate
Re-run the db migrations job kubectl apply -f deploy/kubernetes/manifests/db-migration.yaml

I'm a pro. What's bad about this?

Right now, mariadb's root password comes from the secrets.yaml and wrestlingdev uses the root password to run. Ideally, you'd create another secret for mariadb's root password and you'd create a user specifically for wrestlingdev. From a mysql shell> CREATE USER ${username} IDENTIFIED BY '${password}'; GRANT ALL PRIVILEGES ON ${database}.* TO ${username}; FLUSH PRIVILEGES; $database would be wrestlingdev. I'll do this automatically later.