Role Based Access Control (RBAC) is arguably one of the biggest headaches for engineers in a Kubernetes cluster.
However, there are certain ways to make it far easier.
A thread π§΅
However, there are certain ways to make it far easier.
A thread π§΅
Before jumping into that, let's talk about RBAC.
When you're trying to access a Kubernetes cluster and perform an action, it takes two roles:
- Authentication
- Authorization
When you're trying to access a Kubernetes cluster and perform an action, it takes two roles:
- Authentication
- Authorization
Authentication gets you into the cluster. Authorization allows you to perform a certain action in a cluster.
For example, with proper authentication, you can use `kubectl` commands on a Kubernetes cluster, but you may not have permission to actually do anything like list or create Pods. Therefore, you'll need authorization permission.
OpenID Connect (OIDC), which is an authentication standard, is utilized by a ton of different tools to make this process easier.
Azure Active Directory is a great source and can even be used outside of Azure.
Azure Active Directory is a great source and can even be used outside of Azure.
It can be used for both the authentication piece and the authorization piece to ensure that production environments have the proper security from a user, group, and service account perspective.
Check out how to get Azure Active Directory up and running with Azure Kubernetes Service at the link below.
dev.to/thenjdevopsguyβ¦
#kubernetes #azure #devops
dev.to/thenjdevopsguyβ¦
#kubernetes #azure #devops
β’ β’ β’
Missing some Tweet in this thread? You can try to
force a refresh
γ
