Challenges Managing Multi-Tenant Clusters
Without a strategy in place, it will introduce a handful of challenges. Platform teams will be unable to do the following:
- Consistently manage users, permissions, or policies consistently across cloud clusters
- Determine which users have access to which clusters, resources, or applications
- Configure the right level of access to users to perform their job duties
- Limit or manage resource use to sufficiently plan cluster capacity
- Govern pod network access
Tips for Defining Multi-Tenant Policies
As you’re defining policies for multi-tenant AKS, EKS, or GKE clusters, consider these tips:
- There is no “one size fits all” type of governance framework. Different organizations, as well as different teams within the same organization, can have differing governance and access control requirements depending on the type of industry or organizational structure they are in.
- Access requirements for different roles will evolve as employees change job roles or responsibilities, or leave the company.
- You’ll want to define and implement policy at the top level, as well as create lines of separation across clusters. This not only allows for a consistent governance framework across the enterprise, but empowers division of labor across a wide variety of roles and projects.
Best Practices for Managing Multi-Tenant Clusters
To help you get started on the right track, we created this cheatsheet for multi-tenancy success. In it, you’ll learn how to deliver governance and standardization across your AKS, EKS, or GKE clusters, including:
Managing multiple clusters and access levels can be a daunting task, but it doesn’t have to be so hard. By following these best practices in the cheatsheet, you can make it easier for your platform teams to delegate management and responsibilities at various levels to those that require them.