Annotating Services: Is there a way to configure additional labels and annotations for the services generated by Everest?
Backup Retention Count: I noticed that I can select a retention count for MySQL backups, but not for PostgreSQL. Could you please clarify why this difference exists?
This is a good idea. It might be quite a heavy lift though. Everest relies on various tools underneath - OLM, Operators, etc. It means that to have all the resources properly labels or annotated, we need to instruct these tools to label all the resources properly. We will look into it.
Thank you for that. I checked out the ticket and the description may be a bit confusing. What I mean is that I would like to be able to add my own annotations and labels to services created so I can expose these services over Tailscale for example. It would just be great if we could add our own labels/annotations and maybe also affinity rules etc.
Yes especially for services. In the future adding things like taints/tolerations etc would also be immensely useful for people. Right now we have a dedicated cluster for everest but some people may opt to run this in a shared cluster.
But being able to add custom labels / annotations to generated services etc would be absolutely amazing.
Any updates on this? Every time we create a new database we have to manually add Tailscale annotations to the service which is cumbersome and not really safe. Our other cluster rely on the ability to talk to these DB services via their Tailnet service which can only safely be added via annotations.
Thank you very much for the feedback! My name is Peter and I’m the product manager for Percona Everest. I have discussed your request with Everest team and we have created a roadmap item to allow adding user annotations to the database deployment. I will keep you posted once we have this issue in our pipeline.
Hey @Peter_Szczepaniak, just checking in to see if there’s any update on this?
This feature is really essential for anything beyond basic Kubernetes usage — things like external-dns, cloud provider load balancers, firewalls, and others all rely on annotations on Services to work properly.
I also came across a related Jira issue from back in 2023 (#548). Curious if there’s been any progress or if it’s still on the roadmap? As this really limits the use case
Thanks for checking in on this and welcome to Everest community! This is still on our radar but as always some priorities took over and it never got proper planning. We’ve recently received contribution to Everest operator that allows users to add annotations but only thru CR. This caused us to restart the conversation about adding this to Everest UI and API. In the upcoming week we will be planning Q3 roadmap and this item is one of the proposed features. Once it’s planned this jira issue should have fix version assigned but I’ll also try to remember to post an update here.
Just to note, I was the one who submitted the PR with those changes, as I required the functionality to use Everest effectively. Good to hear it’s being considered for the roadmap.