Valkey
Version 7, 8.0
ClusterControl supports Valkey, an open-source (BSD) high-performance key/value datastore and Redis alternative, designed for high availability and automatic failover. ClusterControl handles the entire installation process, simplifying the setup and management of your Valkey-based environment.
Tech highlights
Distributions
- Valkey Cluster
Replication types
- Asynchronous replication
Top features
- Scaling cluster
- Backup management
- Performance metrics
- User Access Control management
Key features list
| Licenses | |
| Open Source |  |
| Cluster management | |
| Deploy / import cluster | |
| Add / remove / promote node | |
| High availability | |
| Automated failover | |
| Asynchronous replication | |
| Backup / restore | |
| Full backups | |
| Backup compression / encryption | |
| Local / cloud backups | |
| Observability | |
| Infrastructure / database monitoring | |
| Dashboarding / alerting | |
| Security / compliance | |
| Role-based access control | |
| Key management | |
| LDAP integration | |
| TLS encryption | |
| Reporting | |
| Audit log | |
Want some CC for Valkey information for later?
I rarely take a backup of my Valkey instances, and see you have that option. Can I use it, and how complicated is it?
You can schedule Valkey backups or execute on-demand copies from the replica or primary nodes automatically. Store them locally or straight to the cloud, ClusterControl will take care of it all.
We monitor our Valkey instances from the CLI. Does ClusterControl offer any option to monitor in addition to deploying?
ClusterControl monitors real-time with customizable intervals commands per second, total keys, connected clients, blocked clients, memory used & replica lag. You can also integrate / execute your own scripts on all nodes via s9s CLI.
With our current Valkey instances, we adjust the configuration according to the business activity. How is this done in ClusterControl, if it’s available?
Not only is it available, but you can edit the parameters on all instances from a single window, ensuring all instances have the same config for things like binding to localhost for security reasons.