.. | ||
00_namespace.yaml | ||
10_pvc.yaml | ||
30_configmap_nginx.yaml | ||
40_deployment_zammad.yaml | ||
42_deployment_memcached.yaml | ||
43_deployment_postgesql.yaml | ||
50_statefulset_elasticsearch.yaml | ||
60_cronjob_backup.yaml | ||
80_svc.yaml | ||
90_ingress.yaml | ||
Readme.md |
Zammad kubernetes example deployment
This is a proof of concept of a Kubernetes deployment, which should be considered beta and not ready for production.
Prerequisites
- Kubernetes 1.8.x Cluster with at least 1 worker node, 2 CPUs and 6 GB of RAM
- Change the ingress to your needs
Deploy Zammad
Install on Minikube
- Install kubectl
- Install Minkube
- minikube start --memory=6144 --cpus=2
- minikube addons enable ingress
- echo "$(minikube ip) zammad.example.com" | sudo tee -a /etc/hosts
- kubectl apply -f .
- minikube dashboard
- switch to namespace "zammad"
- open "Overview" and wait until all pods are green
- access zammad on:
Install on Google Kubernetes Engine
- connect to cluster via gcloud command
- kubectl proxy
- kubectl apply -f .
- open dashboard in browser
- if everything is green add backends / ingress rules to create external endpoint
If you want to help to improve the Kuberntes deployments here are some todos:
- add cpu & mem limits
- add rolling upgrade strategy to deployments
- add RBAC