| |
| 🔗 Stories, Tutorials & Articles |
| |
|
| |
| Developer Experience Is Security |
| |
| |
"Security at the expense of usability comes at the expense of security." |
|
| |
|
| |
|
| |
| Get Started with eBPF— CNCF Roadmap |
| |
| |
You’ll learn about how Calico uses eBPF and changes the behaviour of the Linux kernel, and the benefits this provides. |
|
| |
|
| |
|
| |
| Who monitors the monitoring system? — Is my Prometheus alive at all ✅ |
| |
| |
There is a simple question that will lead to a never ending loophole when it comes to monitoring systems: “Who monitors the monitoring system”? The answer is not that easy, as our first instinct would be to add a system that monitors our monitoring system. But then, who monitors that system? That is a rabbit hole (some have theorized that it will produce actual wormholes in the fabric of the spacetime continuum). This problem however does have an answer: Implementing a Dead Man’s Switch concept |
|
| |
|
|
| |
|
| |
| Shades of DevOps - Related Job titles |
| |
| |
Dev(sec)Ops: everything you do to overcome the friction created by silos … All the rest is plain engineering |
|
| |
|
|
| |
|
| |
| Best Practices for Multi-tenancy in Argo CD |
| |
| |
Argo CD’s ease-of-use has led many teams to view it as the easiest gateway to GitOps. With that, we’ve seen many different ways of using Argo arise with more and more questions around Multi-tenancy as DevOps teams look at how best to enable their engineers to take advantage of Argo CD. When it comes to multi-tenancy there are a few key things teams should consider when architecting and understanding what multi-tenancy in Argo CD is designed to do, and where limitations exist. |
|
| |
|
| |
|
| |
| A Journey Of Selecting Tool To build ‘Load Test As A Service’ |
| |
| |
This write up is dedicated to the journey the Capillary team took to select the performance benchmarking tool to develop highly scalable and customisable setup — “Load testing as a Service”. |
|
| |
|
| |
|
| |
| Pets vs. Cattle: The Future of Kubernetes in 2022 |
| |
| |
In DevOps, infrastructure is often viewed as pets or cattle. How is this analogy directing trends in the Kubernetes and cloud native ecosystem? |
|
| |
|
| |
