ApexKube journal
Managing Kubernetes for Multiple Clients? Keep Each Client's Access Separate
When you manage Kubernetes for multiple clients, access control gets harder as the number of environments grows. Here's how to keep permissions scoped and secure.
When you manage Kubernetes for multiple clients, access control gets harder as the number of environments grows.
An engineer might need to troubleshoot a production issue for one client but have no reason to access another client’s cluster. A DevOps lead might need broad access across several environments, while a developer only needs access to one namespace.
Giving everyone the same permissions is easier to set up, but it creates unnecessary risk. Managing permissions separately for every person, cluster, and client takes time, too.
The goal is simple: each person should have access to the environments and resources they need, and nothing beyond that.
One Team, Multiple Clients, Different Access Needs
Consider an MSP managing Kubernetes infrastructure for three clients.
- Client A: An engineer needs to investigate a failing application in production.
- Client B: A developer needs to check logs in a staging namespace.
- Client C: A senior engineer manages cluster configuration and deployments.
These people have different responsibilities. Their Kubernetes permissions should reflect that.
The engineer working on Client A’s production issue shouldn’t automatically receive access to Client B’s cluster. The developer checking staging logs shouldn’t need permission to change production resources.
This sounds straightforward, but it becomes harder to maintain when teams manage more clusters, onboard new employees, or change responsibilities.
Kubernetes RBAC Helps, But Permissions Need Attention
Kubernetes has Role-Based Access Control (RBAC) to determine what users and service accounts can do within a cluster.
A Role defines permissions within a namespace, while a RoleBinding grants those permissions to a user, group, or service account in that namespace. A ClusterRole can define permissions that apply at the cluster level or can be reused through bindings.
For example, a developer who only needs to view application resources in the staging namespace may not need permission to modify deployments or access other namespaces.
A namespace-scoped RoleBinding can help provide that access without granting broader permissions.
However, creating the right roles is only part of the job. Teams also need to check how those roles are assigned, who can grant permissions, and whether old access is still needed.
RBAC controls what an identity can do within a cluster. It does not, by itself, provide complete isolation between separate customer environments. Teams must also consider cluster boundaries, shared infrastructure, and the permissions available to administrators.
Five Things to Check When Managing Client Access
1. Keep Permissions Limited to the Required Work
Start by asking what the person actually needs to do.
Someone investigating an application issue may only need to view pods, events, and logs in a particular namespace. They may not need permission to delete workloads, modify deployments, or access cluster-wide resources.
Grant the permissions required for the task rather than starting with broad access and trying to restrict it later.
2. Keep Track of Which Client Each Permission Belongs To
When teams manage several customer environments, they need to know which cluster and namespace a person can access.
Use clear role assignments and keep permissions scoped to the intended environment. If customers have separate clusters, verify that the access configuration doesn’t unintentionally grant an engineer access to another customer’s cluster.
Don’t rely on naming conventions alone to enforce isolation. The actual permissions and cluster boundaries must provide it.
3. Review Access When Responsibilities Change
An engineer who worked on a project six months ago may no longer need access to it.
When someone changes teams, finishes a project, or leaves the organization, review their permissions and remove access that is no longer required.
This is especially important for MSPs, where employees may work across different customer environments over time.
4. Set an Expiry for Temporary Access
Some access is needed only for a specific task: investigating a production incident, debugging a deployment, or helping a client with a configuration issue.
If that access remains active after the task is complete, it creates unnecessary exposure.
Where possible, use time-limited access so permissions expire automatically. If your current setup requires manual revocation, make sure there is a clear process and an owner responsible for removing access.
5. Know Who Has Access and Why
When a client asks who can access their Kubernetes environment, the team should be able to answer without manually checking multiple configuration files and clusters.
Keep track of assigned roles, permission scope, and access changes. Review this information regularly, particularly before client security reviews or audits.
Clear records also make it easier to investigate unexpected access and understand why a person had a particular permission.
How ApexKube Helps Manage Access Across Clusters
ApexKube brings Kubernetes access management and multi-cluster operations into one platform.
With its RBAC and Just-in-Time (JIT) access capabilities, teams can manage permissions and provide temporary access for work that doesn’t require permanent privileges. Access can be scoped to the intended cluster or namespace, with an expiry time so it doesn’t have to remain active indefinitely.
ApexKube also provides a central place to work with multiple Kubernetes clusters rather than treating every environment as an entirely separate management task.
For MSPs, this can make it easier to manage access across customer environments while keeping permissions tied to the work each person needs to perform.
The Exact Setup Still Matters
Before Granting Access to Another Client Environment
The next time someone requests access, check four things:
- Which client and cluster do they need to access?
- Which resources and actions are required for the task?
- How long should the access remain available?
- Who will review or remove that access when the work is complete?
These checks help prevent unnecessary permissions from accumulating as your Kubernetes environments grow.
If your team manages Kubernetes for multiple clients, take a look at ApexKube and see how it handles access management across clusters.
Schedule a meeting with the ApexKube team →
Further reading: Kubernetes RBAC documentation
Keep reading
More from ApexKube
ApexKube journal
Your Last Compliance Scan Is Only True for the Day It Ran
Most teams run a compliance scan before an audit or a client's security review. That report tells you your clusters met the baseline on one day. It doesn't tell you where you stand today.
ApexKube journal
Your Kubernetes Backups Are a Lie Until You've Tested a Restore
A backup dashboard full of green checkmarks doesn't mean disaster recovery works. Here's why you must test your Kubernetes restores and how ApexKube automates the process.
ApexKube journal
Just-in-Time Kubernetes Access: A Safer Way to Manage Temporary Production Access
Give engineers the production access they need, exactly when they need it without leaving elevated permissions behind.
