Kubernetes research platform
A full application, deployed the way production should be.
- Why
- Most Kubernetes examples stop at a single container. We wanted a realistic multi service app to test manifests, routing and storage properly.
- What we built
- We took an existing research app to Kubernetes: frontend, API and database as separate workloads, with declarative manifests, ingress routing and persistent volumes that survive restarts.
- Kubernetes
- Docker
- React
- Flask
- MySQL
$ kubectl get pods
NAME READY STATUS RESTARTS
frontend 1/1 Running 0
api 1/1 Running 0
database 1/1 Running 0
$ kubectl get pvc
NAME STATUS CAPACITY
data Bound 10Gi