Kubernetes RBAC Compared To Docker Swarm RBAC

This article is part of the series that compare Kubernetes and Docker Swarm features.

Docker has RBAC. Just as Kubernetes, it is organized around subjects, roles, and resource collections. In many aspects, both provide a very similar set of features. Should we quickly declare it a tie?

There is one crucial difference between Kubernetes RBAC and the one provided by Docker. The latter is not free. You’d need to purchase Docker Enterprise Edition (EE) to secure your cluster beyond “only those with the certificate can access it.” If you do have Docker EE, you already made up your mind, and the discussion whether to use one or the other is over. Docker EE is great, and soon it will work not only with Swarm but also with Kubernetes. You bought it, and there’s not much reason to switch to something else. However, this comparison focuses on what open source core versions can offer. It ignores third party and enterprise additions.

If we stick with “only what’s in the box” comparison, Kubernetes is a clear winner. It has RBAC, and Docker Swarm doesn’t. The problem is not that Swarm doesn’t have RBAC, but that it doesn’t have any user-based authentication baked in. Therefore, this is a very short comparison. If you don’t want to purchase enterprise products, and you do need authorization and authentication mechanism, Kubernetes is the only option. Just as with Namespaces, Kubernetes shows its strength by the sheer number of features that do not exist in Swarm.

The DevOps 2.3 Toolkit: Kubernetes

The article you just read is an extract from The DevOps 2.3 Toolkit: Kubernetes.

The goal of the book is not to convince you to adopt Kubernetes but to provide a detailed overview of its features. I want you to become confident in your Kubernetes knowledge and only then choose whether to embrace it. That is, unless you already made up your mind and stumbled upon this book in search of Kubernetes guidance.

The book is about running containers at scale and not panicking when problems arise. It is about the present and the future of software deployment and monitoring. It’s about embracing the challenges and staying ahead of the curve.

Give it a try and let me know what you think.

7 thoughts on “Kubernetes RBAC Compared To Docker Swarm RBAC

  1. Pingback: Kubernetes Pods, ReplicaSets, And Services Compared To Docker Swarm Stacks | Technology Conversations

  2. Pingback: Kubernetes Deployments Compared To Docker Swarm Stacks | Technology Conversations

  3. Pingback: Kubernetes Ingress Compared To Docker Swarm Equivalent | Technology Conversations

  4. Pingback: Kubernetes Secrets Compared To Docker Swarm Secrets | Technology Conversations

  5. Pingback: Kubernetes ConfigMaps Compared To Docker Swarm Configs | Technology Conversations

  6. Pingback: Kubernetes Namespaces Compared To Docker Swarm Equivalent (If There Is Any) | Technology Conversations

  7. Pingback: Kubernetes Resource Management Compared To Docker Swarm Equivalent | Technology Conversations

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s