Hello everyone,
I’ve enalarged the DB PV following this tutorial: Percona Operator Volume Expansion Without Downtime
The disks are resized and pods have increased their size. Unfortunately the Everest UI continues to show me the old size and it causes errors in the Statful set. I’ve watched everywhere but i cannot find any kind of settings to manually override the disk size from the UI. It’s a blocking issue because without an healty cluster, i cannot execute any kind of backup from your tools.
Thanks in advance for your suggestions.
Best regards
Davide
Hello @daccetturi, starting from Everest 1.6.0 (planned to be released this week) you’ll be able to change the disk size directly from the UI/API/CRD without having to go through the tutorial you followed.
This will also solve your issue so I suggest you update to 1.6.0 when it comes out in a few days.
2 Likes
Hello Diogo,
Many many thanks for your reply.
I will update to 1.6.0 as soon as it will become available.
Regards
Davide
1 Like
Hello @Diogo_Recharte,
I’ve updated the env this morning. I can find the button to change the size but i always obtain this error: DatabaseCluster.everest.percona.com “my-db” is invalid: spec.backup.enabled: Required value.
How can i fix it?
Many thanks in advance.
Davide
Hi @daccetturi !
Did you install Everest with Helm?
If so most probably your CRDs were not upgraded so you will need to do it manually because Helm upgrade doesn’t update CRDs.
Here info how to do it: Upgrade Percona Everest using Helm - Percona Everest
Regards,
Tomislav
It works like a charm!
Many thanks
Sorry @Tomislav_Plavcic but after the pod’s update, i always obtain this string:
2025-04-18T09:06:54.803Z INFO reconcile replication error {“controller”: “pxc-controller”, “namespace”: “cercafarmaco-stage”, “name”: “mysql-cercafarmaco”, “reconcileID”: “0b99b633-b7b1-4957-b7ff-da40f28d7480”, “err”: “failed to ensure cluster readonly status: connect to pod mysql-cercafarmaco-pxc-0: dial tcp: lookup mysql-cercafarmaco-pxc-0.mysql-cercafarmaco-pxc.cercafarmaco-stage on 10.43.0.10:53: no such host”} is there any way to definitely solve the issue?
Many thanks
Davide