3 ms·
Best way to run database is in static pods. You'll get all the benefit of kubernetes ecosystem (monitoring, logs, inventory, access control) without any drawbac
by rossmohax 5y ago
Best way to run database is in static pods. You'll get all the benefit of kubernetes ecosystem (monitoring, logs, inventory, access control) without any drawbacks.
- peterthehacker 5y agoYou mean without a deployment or statefulset? How would you connect to the DB without a service providing a persistent DNS name?
- merb 5y agoyou can create a static pod manifest in /etc/kubernetes/manifests (https://kubernetes.io/docs/reference/setup-tools/kubeadm/implementation-details/ https://kubernetes.io/docs/reference/setup-tools/kubeadm/imp...) these manifests can be targeted with a Service. However my preferred solution for databases inside k8s is still zalando-operator with spilo and local storage. it's rock solid. I once used kubedb and lost the database because of bugs, so I'm staying away from them. Crunchy looks solid aswell but it looks like it's a little bit more polished but harder to configure than zalando's solution which is more built to their needs.
- rafaelturk 5y agoYou can create a service point to the `pod` tag. Or a manifest.