waqar
@waqar-proDevOps & Cloud Engineer | AWS | Kubernetes | Docker | Terraform | CI/CD | Security | Automating infrastructure at scale ☁️
Language Breakdown
Lines of code distribution across 17 owned repositories
T-Shaped Developer
T-shapedDeep in JavaScript with broad versatility
Collaboration Network
Global Impact visualization
Repos
18
PRs
0
Growth
+18%
Top Collaborators
No collaborator data yet.
Coding Streak
Contribution activity over the past year
Christian Deacon
@gamemann
Maher
@Maher-Elmair
Foyez kafi
@foyezkafi
Alp ₿📈🚀🌕
@IDouble
MrWhite
@mrwhite4939
Top Repositories
I recently completed a hands-on DevSecOps project that gave me practical experience with modern CI/CD practices. The project involved building an automated pipeline for a Netflix clone application using industry-standard tools.
I applied all the policies — but traffic was still flowing freely. 😤
And that single 'no' made me understand why RBAC exists.
Kubernetes is not just a tool — it's a mindset of resilience and scalability. 💪
The fix is simple but powerful — give each application its own identity with proper access control.
Most people deploy pods without thinking about who is running inside the container. By default, Kubernetes runs containers as ROOT with full access to the filesystem and all Linux capabilities. That is a serious risk.
This is not just a concept — this is exactly how Netflix, Uber, and every cloud-native company routes millions of requests daily.
kubectl apply → API Server → Admission Webhook → Allow ✅ or Block ❌
I didn’t just study Kubernetes security — I applied, tested, and validated it in a real-world scenario...
Two powerful security layers implemented
Open Source Impact
Contributions to external projects
