Hyperglance Kubernetes Migration (RKE2)
The Kubernetes migration is now available.
This migration moves Hyperglance from Docker Compose to Kubernetes (RKE2).
If you completed Update 1-2025, you’re ready to migrate. If not, do that first.
What's Happening?
This update is about migrating the internal orchestration layer of Hyperglance.
If you are running Hyperglance on an AWS Instance, Azure VM or GCP VM today, then it is internally running a set of containers orchestrated by Docker Compose.
With this update, we will be migrating over to a lightweight version of Kubernetes called RKE2 — the secure, production-grade Kubernetes distribution from Rancher.
Migration Guide
You have 3 options available to you.
It's important you read our step-by-step guide to migration.
Why Are We Making This Change?
Hyperglance is growing! We want to provide new features and scale across modern environments of all shapes and sizes.
We have found Docker Compose is no longer meeting our requirements, so we are moving to RKE2 and packaging our app as a Kubernetes Helm Chart. This approach offers much more flexibility in how we architect Hyperglance going forwards.
In fact, this update sets the stage for many exciting things to come, including:
- Future support for AI workloads
- Better integration with tools like Snowflake
- FinOps for Kubernetes
- More flexible multi-tenancy for MSPs
- Greater horizontal scalability
- Improved data handling and microservice deployment
This will also bring a consistent user experience across different types of deployments -
Whether you deployed Hyperglance as an Instance or VM or onto your own Kubernetes cluster.
What’s Included in the Update
- Migration from Docker Compose to Kubernetes (RKE2)
- A brand-new Hyperglance CLI tool for managing your deployment: Start, stop, update, admin users — all from one tool.
What You’ll Need to Do
As the update is released, Hyperglance will pop a notification with a guided process to migrate Hyperglance from Docker Compose into RKE2. Don't worry - We'll make it easy.
We’ll provide:
- Clear steps with terminal commands you can copy/paste
- In-product prompts to guide you through the migration
- Help if anything doesn’t go to plan
If You Haven’t Completed Update 1-2025 Yet: Please do that first. The OS upgrade and container changes are required before this update can be applied.
What If You Don’t Update?
You can continue using the Docker-based version for now. We’ll support it for a limited time, but new features and improvements will only be released for the Kubernetes version.
Expect occasional reminders in the product if you’re still on the legacy Docker Compose stack.
Questions?
Not sure what this means for your setup? Our support team is ready to help — get in touch any time.