In our final article on Kubernetes RBAC, we are focusing on RBAC itself. Everything else in the series led towards this key piece. In part one we discussed authentication and authorization on a high level and in part two we focused specifically on authentication. Now let’s dive into authorization.

Many organizations are looking to implement DevOps due to the promise of increased release velocity, better developmental agility, and the ability to free up time for developers to focus on innovation. However, adopting DevOps isn’t a panacea— instead, the idea of communication, collaboration, and blameless retrospectives that a DevOps model encourages can help foster a leaner system where bottlenecks are solved in a manner that not only fixes the problem, but also improves the process.

As various teams within your organization are discovering new ways to leverage Kubernetes, they’re adopting a growing number of clusters to support their project efforts. Unfortunately, this is where many of the challenges begin. While managing one Kubernetes cluster is not trivial, trying to manage multiple Kubernetes clusters across multiple environments becomes exponentially more difficult.

HAProxy gives you an arsenal of sophisticated countermeasures including deny, tarpit, silent drop, reject, and shadowban to stop malicious users. There are two phases to stopping malicious users from abusing your website and online applications. Step one is detection, step two is deploying countermeasures. HAProxy is more powerful than nearly every other load balancer when it comes to both detection and countermeasures.

When planning the SRE from home virtual even last month, one of the central themes was wellness and the need for self-care for SREs, especially during this time of crisis. Knowing how stressful an SRE’s day can be, combined that with a global pandemic and new working conditions, we knew we needed programming around SRE and IT wellness for SRE from Home. We’re all looking for ways to maintain a healthy work-life, but hearing this from your peers was especially important.

Anyone who’s ever played the game of chess knows there’s more than one way to reach a desired outcome. There are 400 possible setups after the first turn; 197,742 after the second; and just north of 120 million after the third—all of which are marching toward the same desired outcome. “So, what does any of this have to do with DevOps?” you ask? Fair question.

How much does your Kubernetes service cost to operate? This seems like a simple question, right? It’s one thing to say how much your Kubernetes cluster itself costs to operate — that, after all, is a group of real servers, associated with a specific number.