Hyperglance Tech Stack Migration
Migration to our latest architecture is now available.
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.
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.
What’s Included in the Update
- Migration of internal orchestration layer from Docker Compose to RKE2.
- A brand-new Hyperglance CLI tool for to simplify managing your deployment.
- Improved security - The RKE2 architecture has additional security measures that are not possible to implement with Docker Compose.
- Future-proof architecture.
What You’ll Need to Do
Follow our step-by-step guide to migration and if you get stuck or need help just get in touch.
What If You Don’t Update?
You can continue using the Docker-based architecture for now. We will continue to support it for a time but in the future new features and improvements may only be released for the new architecture.
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.