Run using kubernetes / minikube

Installation / Starting Minikube (tested for windows)

choco install minikube

choco install kubernetes-cli

choco install kubernetes-kompose

Navigate to the location where the docker-compose file is. It should be under ‘C:...qunicorn-core’.
Now check if a minikube folder has been created under ‘C:...qunicorn-core’.
If not, create the kubernetes configuration files. This will generate a folder called minikube with all the kubernetes configuration files based on the docker-compose. However this might overwrite custom changes made to the files, if already existing. Proceed with caution.

kompose convert -f docker-compose.yaml --out minikube

minikube start

Set minikube as docker env
Minkube needs to be set as docker environment to be able to build images for minikube. Otherwise Minikube would not be able to find the images. This needs to be done every time a new terminal is opened.

minikube docker-env | Invoke-Expression

docker build -t qunicorn:local .

Start services and pods with configuration (Note that starting the whole cluster can take a while (up or more than 8min))

kubectl apply -f minikube

Expose qunicorn through minikube (start in another terminal) Exposes the qunicorn service to the internet. This is needed to be able to access the service from outside the cluster.

minikube tunnel

kubectl get svc

kubectl get po --selector=io.kompose.service=server

Now you can access qunicorn using [EXTERNAL-IP]:8080/swagger-ui of the server service (usually you can use localhost)

kubectl delete daemonsets,replicasets,services,deployments,pods,rc,ingress --all --all-namespaces

minikube service {service}

minikube dashboard