What's new in OpenEverest 1.13.0
➡️ New to OpenEverest? Get started with our Quickstart Guide.
Expand to unleash the key updates
📋 Release summary
| # | Category | Description |
|---|---|---|
| 1. | Pod Logs Viewer | View real-time logs from database pods directly in the OpenEverest UI for easier troubleshooting and monitoring. |
| 2. | Dynamic value injection in LoadBalancerConfig | Use Go templates in LoadBalancerConfig annotations to dynamically inject cluster-specific values. |
| 3. | OpenEverest Rebranding | Full rebranding from Percona Everest to OpenEverest across all repos and documentation. |
| 4. | Operator upgrades | Support for Percona XtraDB Cluster Operator v1.19.0. |
| 5. | New features | Check out the new features introduced in OpenEverest 1.13.0 |
🌟 Release highlights
- 📜 Pod Logs Viewer
- 🔧 Dynamic value injection in LoadBalancerConfig
- 🎨 OpenEverest Rebranding
- ⚙️ Operators
View pod logs directly in the UI
OpenEverest now includes a built-in Pod Logs Viewer, allowing you to view real-time logs from database pods directly in the OpenEverest UI. This feature simplifies troubleshooting and monitoring by eliminating the need to use kubectl or other external tools to access pod logs.
Key capabilities:
- View logs from any pod in your database cluster
- Filter logs by container
- Stream logs in real-time
- Search and navigate through log history
- Copy logs for further analysis
This feature significantly improves the operational experience, making it easier to diagnose issues and monitor database cluster health.
📘 Related GitHub issue: #1765
Go templating support for LoadBalancerConfig annotations
LoadBalancerConfig now supports Go templating in annotation values, enabling dynamic value injection based on the target DatabaseCluster's properties. This powerful feature allows you to create reusable configurations that automatically adapt to each database cluster.
Example use case:
When integrating with ExternalDNS, you can now define a single LoadBalancerConfig that generates unique hostnames for each database cluster:
external-dns.alpha.kubernetes.io/hostname: "{{ .ObjectMeta.Namespace }}-{{ .ObjectMeta.Name }}.example.org"
When applied to a DatabaseCluster named my-postgres in the production namespace, this template automatically resolves to:
external-dns.alpha.kubernetes.io/hostname: "production-my-postgres.example.org"
Available template fields:
.ObjectMeta.Name- Database cluster name.ObjectMeta.Namespace- Namespace.Spec.Engine.Version- Database engine version- Any other field from the DatabaseCluster custom resource
This eliminates the need to create separate LoadBalancerConfigs for each database cluster, significantly reducing operational overhead.
📘 For detailed instructions, refer to our documentation.
📘 Related GitHub issue: #1817 Big thanks to @Ankit152 for contributing this improvement!
Complete rebranding to OpenEverest
This release marks the official rebranding from Percona Everest to OpenEverest. All repos, documentation, and user interfaces have been updated to reflect the new branding, reinforcing our commitment to open-source principles and community-driven development.
What changed:
- Product name updated to OpenEverest across all interfaces
- Documentation updated with new branding and URLs
- UI refreshed with OpenEverest branding
- Issue tracking migrated to GitHub Issues exclusively
New features
-
#1765: OpenEverest now includes a Pod Logs Viewer, allowing users to view real-time logs from database pods directly in the UI for easier troubleshooting and monitoring.
-
#1817: LoadBalancerConfig annotations now support Go templating for dynamic value injection based on DatabaseCluster properties, enabling reusable configurations that automatically adapt to each cluster. (Thanks @Ankit152!)
-
OpenEverest now supports Percona XtraDB Cluster Operator v1.19.0.
🚀 Ready to Upgrade?
Upgrade to OpenEverest 1.13.0 to access these new features and improvements.
📖 Explore our Upgrade section for the upgrade steps.