DZone

Identity and access management are critical components of many applications. However, enterprise companies that are using multiple EKS, AKS, or GKE cloud Kubernetes clusters for various projects may find it challenging to identify the right level of access for different users, especially when there are multiple users and groups of users who are coming, going, and moving between teams.  

As teams expand their usage of Kubernetes, clusters and workloads will exist in different environments. One team may be building their stack on cloud provider “A,” while another team is building a stack on cloud provider “B.” Even on a single public cloud service, clusters may exist in different environments, and IT isn’t even aware of these things. This makes tracking all of the individual logins and permissions across the organization next to impossible, especially when there are multiple accounts and access levels to manage. And the problem only grows in complexity as more people on-board, off-board, or change teams, and projects multiply.

Source: DZone