Context
My final year project set out to answer a simple question: what would Kubernetes look like if developers never had to open a terminal or write YAML?
The problem
Kubernetes is powerful, but the day to day experience for developers is hard:
- Deploying needs
kubectl, cluster credentials and a pile of manifests. - Every service copies and tweaks the same YAML, and mistakes reach production.
- Logs and status are scattered across commands most developers do not remember.
What I built
A web platform on top of the Kubernetes API. Developers manage workloads from the browser: create a deployment, set replicas and resources, expose it and watch its status.
Integrated CI/CD. Connecting a repository builds the image and deploys it, so a push becomes a running workload without anyone writing a pipeline by hand.
Guardrails by default. The platform generates the manifests, so resource settings, labels and health checks are consistent across every service.
Logs and status in one place. Each workload page shows its pods, events and logs without leaving the browser.
The result
- Built and presented as my final year project.
- The same idea now shapes how I build internal developer platforms for teams.
Stack
Kubernetes, Docker, CI/CD pipelines, a web frontend and backend on top of the Kubernetes API.