Connect to multiple clusters simultaneously, as if it was one big cluster

It's common to see teams deploying their services across multiple clusters. It might be for redundancy, scalability, or simply to separate different environments. But this comes with a cost: managing multiple clusters is a pain.

With pain also comes the creativity to solve those problems. Automation, GitOps and Infrastructure as Code has come a long way to alleviate this pain from an infrastructure point of view. But what about the engineers who interact with the cluster?

kubectl is the defacto standard for interacting with Kubernetes clusters. But it is not the most user friendly tool when it comes to managing multiple clusters as you have to constantly switch context between one cluster and the other, as well as remembering which cluster you are currently connected to.

What if we could connect to multiple clusters at once?

We started Aptakube to answer this simple question. When you open the app on your desktop, the first thing you see is a list of all your clusters. From there you can select not just one, but as many clusters as you want!

Screenshot of Aptakube showing multiple clusters being selected simultaneously

Aptakube follows a zero-config model:

  • It works with your existing Kubeconfig;
  • There is nothing to install on your clusters;
  • They don't need to be interconnected in any way;
  • They can even be in different regions or clouds, it doesn't matter!

What's so special about this feature?

For starters, it allows you to type less and move faster. There is no more context switching or having to remember which cluster you are currently connected to. Combined with the rich resource view in Aptakube, you can view all your resources across all your clusters in one place.

Imagine a scenario where your application is deployed to two clusters, one in America and another in Europe. Some users are reporting an issue with your app and you want to investigate. With Aptakube, you can select both clusters and view pods from both clusters and see if there is any correlation between the two, or if any pod in any cluster is in a CrashLoopBackOff state, for example.

Screenshot of Aptakube showing pods from two clusters in one view

It is a feature that we believe will make a huge difference in the way engineers interact with their clusters and we invite you to give it a try!

Tired of using Kubectl? 😓

Give Aptakube a go — a modern, lightweight Kubernetes interface.

Screenshot of Aptakube showing a list of pods from 2 clusters in a single view