I used git: GitHub - Bahmni/bahmni-k8s: Bahmni on Kubernetes and follow the step
when i run it then I face this error ImagePullBackOff
bahmni-k8s$ kubectl get all
NAME READY STATUS RESTARTS AGE
pod/bahmni-web-9cbb97955-gng5n 1/1 Running 1 (6m18s ago) 17h
pod/odoo-66b9f598ff-c6g4d 0/1 ImagePullBackOff 0 17h
pod/odoo-connect-6f4457b98b-ggfj5 0/1 ImagePullBackOff 1 (6m18s ago) 17h
pod/odoodb-56fbc896dc-6fxqk 1/1 Running 1 (6m18s ago) 17h
pod/openelis-66654dc45f-8v96j 0/1 ContainerCreating 0 17h
pod/openelisdb-5d7994c74f-cps8h 1/1 Running 1 (6m18s ago) 17h
pod/openmrs-77dd964f95-tdzz9 0/1 ImagePullBackOff 0 17h
pod/openmrsdb-5848c77797-zbcns 1/1 Running 1 (6m18s ago) 17h
bahmni-k8s is no longer maintained, I have archived the repo with deprication notice. Please refer this document to run bahmni cluster locally using Minikube.
Can you share more details on your intend to try Bahmni with Kubernetes - do you plan to run Kubernetes cluster in production eventually? What cloud provider are you considering?
Hello @n0man, minikube runs a single node and as per this document here it is discouraged when it comes to production environments because it has a risk of a single point of failure but kind can run a multi node k8 cluster is this a tested viable option.
So the risk of single point of failure is due to the fact that tools like Minikube and even Kind (Kubernetes in Docker) are designed targetting a single machine architecture - more with the objective of spinning up a lightweight K8s cluster for local development and testing. For records, you could even use minikube to provision multiple nodes cluster - but that still doesnt change the single point of failure risk for production usage since all of the additional nodes would run under as docker containers (similar to kind). There are many other options in addition to minikube like kind, k0s, MicroK8s, k3s etc but we havent tested any of these since minikube offer enough for local development and testing.
Great @n0man , thanks for the clarification.