When ExternalName is not enough: Kubernetes-native discovery for external workloads
Kubernetes can already point a Service at an external hostname with ExternalName. But what if you want the actual external backends to exist as Kubernetes Endpoin...
Architecture, operations and open source
Production experiences, technical decisions and lessons from the Cloud, Kubernetes and Platform Engineering world.
Kubernetes can already point a Service at an external hostname with ExternalName. But what if you want the actual external backends to exist as Kubernetes Endpoin...
GitHub configuration is platform state. I built github-platform-operator to manage repositories, rulesets, organization members, teams, access, environments, secr...
cmdpeek is a searchable command palette for reusable terminal workflows. It lets you find commands by intent using names, titles, descriptions, labels, and comman...
kubectl-peek now lets you open isolated, context-aware Kubernetes shells backed by temporary kubeconfigs, so you can work across clusters and namespaces without c...
kubectl-peek is an interactive kubectl plugin for inspecting Kubernetes Secrets, optionally hiding their values, and discovering the resources that use, produce, ...
Elastic APM seemed to work perfectly, but errors weren't showing up. The problem wasn't with the agent—it was with log templates.
Many teams use a Terraform structure based on a single repository with folders per environment. While it works, there are more robust alternatives for production ...
Cilium with BPF masquerade can interfere with Workload Identity on GKE, causing Pods to use the node service account instead of the expected one.
Designing how internal and external services are exposed in Kubernetes is key to preserving isolation, security, and operational clarity in GCP.
After rolling out Cilium on both EKS and GKE, one difference became very clear: networking is significantly easier to reason about on GKE.
K8sReady