Hi
I search how to install everest percona with helm Chart. But the only documentation I found, details the installation with everestctl.
Thanks in advance
Hi
I search how to install everest percona with helm Chart. But the only documentation I found, details the installation with everestctl.
Thanks in advance
Hi
Thank you for your question and interest in Percona Everest.
Our team plans to create a helm chart for Percona Everest in version 1.3 in about a month or two.
If you have any special requests or requirements, please share.
You may want to participate in testing, I can send you a PR with the future helm chart when it starts to be developed.
Hi @sbou !
The discussion about the helm chart has been started here: Helm Chart · percona/everest · Discussion #653 · GitHub
and there is also a link for the PoC version.
So you might want to try it out and give some feedback there.
Thanks!
Hi,
Thanks for your response. I’m interested to participate in testing. For the moment, I haven’t special request for yet
Hi @sbou,
We’re excited to share that Percona Everest now supports installation with Helm in our latest release, 1.4.0!
Thanks for your suggestion - here’s what you need to get started:
Let us know how it works for you!
How can I change the deployment from CLI to Helm chart without downtime?
Hi @silent ,
When you upgrade to Everest v1.4.0, your installation will automatically migrate to Helm. Thereafter, you will be able to use Helm to manage your Everest installation.
Depending on how many DB namespaces you have, the upgrade creates multiple helm releases - 1 for the core components (named everest-system
) and 1 for each DB namespaces (named after the namespace), for example:
❯ helm list -n everest-system
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
everest-system everest-system 1 2025-01-10 16:30:42.457573 +0530 IST deployed everest-1.4.0 1.4.0
❯ helm list -n everest
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
everest everest 2 2025-01-10 16:31:06.95247 +0530 IST deployed everest-db-namespace-1.4.0 1.4.0
During the upgrade, the Everest API server and operator pods will restart, but your database clusters will not experience any downtime.
Please remember to use CLI v1.4.0 to perform the upgrade. Feel free to refer to the upgrade guide for more info.
Unanswered | Unsolved | Solved
MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright © 2006 - 2024 Percona LLC. All rights reserved.