$ whoamipranav deo — devsecops engineer, passau
$ cat focus.txtkubernetes · infrastructure as code · observability · security
$ uptimein production since march 2022
$ Infrastructure that's secure by default and boring on purpose.
I move legacy applications onto Kubernetes, automate the infrastructure under them, and build the dashboards that show what's actually happening. Security is a design principle from the first commit, not a checkbox at the end.
Case study
2023 – now
Moving legacy applications onto Kubernetes
Legacy applications moved to managed Kubernetes on AKS and DOKS. GitLab CI/CD handles every deployment, and Grafana, Loki, Tempo and Mimir watch everything once it is running. The aim was never to use Kubernetes for its own sake. It was to make deploys routine and outages explainable.
- 01 · containerise
- 02 · pipeline every deploy
- 03 · observe from day one
Things I've shipped.
kubernetes · aks · doks
Legacy applications, migrated to Kubernetes
Scalable, repeatable deploys on managed clusters.
gitlab ci/cd · gitops
Deployment pipelines teams don't have to think about
Every change goes through a merge request and a pipeline.
grafana · loki · tempo · mimir
An observability stack from logs to traces
Less downtime, and incidents that start with data.
pulumi · ansible
Infrastructure provisioning as code
Environments that are reviewed, versioned and rebuildable.
defender · entra id
Raising the Azure Defender security score
Plus enterprise identity control on Microsoft Entra ID.
iso 27001 · tisax
Compliance documentation that matches reality
Contributions to ISO 27001 and TISAX efforts.
Recent writing.
All posts →Experience
DevSecOps Engineer
Digital Automotive by IT Manufactory
Jan 2023 – now
DevOps Engineer
Digital Automotive by IT Manufactory
Mar 2022 – Dec 2022
Education
M.Sc. Computer Science
Universität Passau · IT Security & Reliability
2020 – 2023
Honours Degree in Entrepreneurship
Universität Passau
2023
Bachelor of Computer Applications
Birla Institute of Technology, Mesra
2016 – 2019
cert · IBM Certified Data Engineer — Big Data Mastery Award
Operating principles
If it isn't in git, it doesn't exist.
Clicking in a console is how drift starts, and drift is how security holes start. I'd rather write the change down, have someone review it, and let a pipeline apply it. That way, when something breaks at 3am, the answer to “what changed?” is one command away.
Security is not a checkbox. It's a property of how the system is built.
plan → build → scan → ship → observe
plan · pulumi preview · reviewed in a merge request build · gitlab ci · every commit scan · defender for cloud · findings tracked to zero ship · kubernetes · aks + doks observe · grafana, loki, tempo, mimir
Tools I actually reach for
Seven tools, nothing else.
- 01
Kubernetes
Where the workloads live, on AKS and DOKS.
- 02
GitLab CI/CD
One file that describes how code gets to production.
- 03
Pulumi
Infrastructure in a real programming language, with types, loops and tests.
- 04
Ansible
For the machines that aren't cattle yet.
- 05
Grafana, Loki, Tempo, Mimir
Logs, metrics and traces in one place, so incidents start with data.
- 06
Microsoft Defender for Cloud
A security score you can actually move.
- 07
Microsoft Entra ID
Identity is the perimeter now.
Working where security meets operations?
I'm always happy to talk with people working at the intersection of security, operations and innovation. Email is the fastest way to reach me.
About
I'm Pranav, a DevSecOps engineer at Digital Automotive by IT Manufactory in Passau, where I also did my master's in computer science. I believe in systems that are understandable, maintainable and collaborative: GitOps, honest dashboards and infrastructure as code. Away from the terminal I'm on a bike exploring new routes or at a chessboard planning my next move.
speaks: hindi · marathi · english · german · a little kannada