How patil2771/devops-challenge works
This repository is a Flask task manager packaged for Kubernetes, with PostgreSQL persistence and a documented CI/CD and monitoring stack. The main user workflow serves the task page and exposes REST endpoints; task reads and writes go through the Flask app to PostgreSQL. The source excerpt confirms those app-level calls, while deployment, storage configuration, CI/CD, and monitoring are represented by the README and file tree only, so their detailed wiring is not asserted.
Main entry points: app.py Flask app · backend.yaml Backend deployment · postgres.yaml PostgreSQL · secret.example.yaml DB secrets
Components 10
Kubernetes platform
- PostgreSQL
k8s/postgres.yaml - Backend deployment
k8s/backend.yaml - DB secrets
k8s/secret.example.yaml
Delivery and monitoring
- Container image
app/Dockerfile - GitHub Actions
.github/workflows/deploy.yml - Prometheus
- Grafana
Other components
- Task user
Connections 10
- Task user → Flask app: requests
app/app.py - Flask app → Task page: renders
app/app.py - Flask app → PostgreSQL: queries and writes
app/app.py - Backend deployment → Flask app: runs
README.md - Backend deployment → PostgreSQL: connects to
README.md - DB secrets → Backend deployment: configures credentials
README.md - Container image → Backend deployment: packages app
README.md - GitHub Actions → Backend deployment: deploys
README.md - Prometheus → Flask app: monitors
- Grafana → Prometheus: visualizes metrics