Day 0 Ops suggests we architect a solution, Day 1 is implementation, and Day 2 is management. When debugging networks after they've been successfully implemented, it's time to start
Arguably, there are two things that every environment cannot live without:
1. Proper network traffic/network handling.
2. Persistent data/databases
From a networking perspective, there's traffic everywhere. It's
As with the majority of architecture, there's a "client/server" model or a "control plane/data plane" model. We see it in our Kubernetes clusters and in
Just about every Kubernetes environment, in some capacity, will have an application stack that needs to be accessed from the outside world (customers) or by internal engineers (e.g., a Backstage environment). In
If you’re implementing a Service Mesh in your Kubernetes environment, chances are it’s for one of the following:
1. Encryption for service-to-service communication.
2. The ability to see network traffic and