Connect your clusters to Roam
Roam connects straight from your phone or desktop to a cluster's API server. Pick how your cluster is run and follow the guide — most take a couple of minutes.
Amazon EKS
Sign in with IAM access keys, MFA, an assumed role or AWS IAM Identity Center, then pick a cluster.
Google GKE
Connect with a service account key: the IAM roles it needs, how to create the key, and what to enter.
Azure AKS
Sign in with device login or a service principal; what the cluster needs and which roles to grant.
Kubeconfig or token
k3s, kind, minikube, on-premises and any other cluster: import a kubeconfig or use a bearer token, with SSH bastion and CA options.
Which one do I need?
- A cluster on AWS, Google Cloud or Azure: use its sign-in. Kubeconfigs for these clusters run a helper program (
aws,gke-gcloud-auth-plugin,kubelogin) to get a token, and a phone can't run it. - Anything else: import its kubeconfig, or use the API server URL and a service-account token.
- On the desktop app downloaded from GitHub or the Microsoft Store, you can also use your
~/.kube/configas it is, helper programs included.
Whichever way you connect, the credentials are encrypted on your device and never go through a Roam server. See the features for what you can do once you're in.
Get Roam
Free on every platform. Your clusters and credentials stay on your device.
Connection guides
- Amazon EKS — Sign in with IAM access keys, MFA, an assumed role or AWS IAM Identity Center, then pick a cluster.
- Google GKE — Connect with a service account key: the IAM roles it needs, how to create the key, and what to enter.
- Azure AKS — Sign in with device login or a service principal; what the cluster needs and which roles to grant.
- Kubeconfig or token — k3s, kind, minikube, on-premises and any other cluster: import a kubeconfig or use a bearer token, with SSH bastion and CA options.