The Problem Most engineers deploy to Kubernetes by clicking buttons in a UI. I built Archnet — a fully automated Internal Developer Platform What is an Internal Developer Platform? An IDP is the infrastructure layer that sits between your code How code gets deployed How secrets are managed How the system monitors itself How failures get detected and fixed Most companies pay Humanitec or Backsta
We had ArgoCD running perfectly. Every deployment was reconciled from Git. Drift detection worked. Rollbacks were one-click. Our GitOps setup was clean. Developers still couldn't provision a staging environment without pinging the platform team. That gap — between "GitOps in place" and "developers can actually self-serve" — is where most platform engineering teams get stuck. GitOps solves a real p
CKS Study Memo on Network Policies official document: https://kubernetes.io/docs/concepts/services-networking/network-policies/ You can control traffic between pods using the NetworkPolicy resource. In the sample manifest, the selectors are written like this. ingress: - from: - namespaceSelector: matchLabels: user: alice - podSelector: matchLabels: