I've spent the last several months studying Kubernetes in depth and plan to take a Kubernetes certification soon. I've already worked through projects involving cert-manager, an API gateway, Cilium, kube-proxy, iptables, networking, and network policies, and I maintain several local clusters. Networking is the part of Kubernetes I enjoy most.
For a serious portfolio project, I'm considering building a privacy-preserving leaked-password monitoring service based on k-anonymity. I have a strong background in cryptography and would like to create something inspired by existing password-breach checking systems, but with a more complete architecture.
I also have experience with Python, ACID and NoSQL databases, RabbitMQ, Git, Ansible, GitLab CI, Proxmox, and KVM. I'm considering building a complete CI/CD system with testing, GitLab pipelines, Kubernetes controllers, Argo CD, security checks, and possibly cloud deployment.
For someone applying to junior DevOps, Kubernetes, or security roles, which project would demonstrate the most useful skills? Would it be better to focus on one substantial project, contribute to existing open-source tools, build a multi-environment cluster setup, or pursue another certification after the first one?
4 Answers
Using your own cluster for a homelab can provide more practical experience than building a narrowly focused demo. Run several services, expose some safely, manage certificates and backups, introduce authentication, and practice upgrades, rollbacks, resource limits, network policies, and disaster recovery.
You can create realistic operational problems yourself: kill workloads, fill a disk, break DNS, rotate certificates, restore a database, or introduce latency between services. Then use monitoring and logs to investigate what happened. That demonstrates the day-to-day skills employers usually want more clearly than simply showing that a dashboard exists.
The password-monitoring idea is interesting, especially because it combines cryptography, privacy, APIs, databases, and distributed systems. I would avoid making it just a Kubernetes deployment, though. Build the application properly, document the threat model, explain how the k-anonymity design protects users, and then deploy it with strong automation and security controls.
For the Kubernetes side, contributing to established projects can make the portfolio much stronger than another isolated demo. Look for beginner-friendly issues involving documentation, tests, bug reproduction, or small fixes. Projects involving networking, certificates, GitOps, observability, policy enforcement, and security would fit your interests well.
A realistic portfolio environment would be a small multi-cluster or multi-environment platform: development, staging, and production-style namespaces or clusters, provisioned with Terraform and deployed through CI/CD. Add Helm, GitOps, secrets management, policy checks, and an observability stack using OpenTelemetry, metrics, logs, and dashboards.
The important part is not running every popular tool. Show that you can make design decisions, automate repeatable deployments, handle failures, secure access, and explain how the system would scale. A clear README, architecture diagram, runbooks, tests, and a few deliberately simulated incidents will make the project much more convincing.
Monitoring is difficult to appreciate on a local cluster because nothing breaks often enough to create useful data. What kinds of failure scenarios would you simulate to make observability meaningful?
A security-focused certification can be worthwhile if it matches the jobs you want, but it should not replace hands-on work. For a junior candidate, one polished project with a working application, infrastructure-as-code, automated testing, deployment, security documentation, and troubleshooting notes is often more useful than collecting several certificates.
Your cryptography background is a differentiator, so use it as the application’s core rather than trying to compete with experienced candidates on every security domain. Pair that project with a practical Kubernetes platform and perhaps a few small open-source contributions. This gives employers evidence of both depth and operational ability.
I’m planning a full CI/CD and GitOps setup with testing, security checks, and possibly cloud deployment. My concern is whether spending a lot of time on advanced networking tools gives enough return for a junior role, even though that’s the area I enjoy most.