KubeBlocks for
etcd
etcd is a strongly consistent, distributed key-value store that provides a reliable way to store configuration data, service discovery, and distributed coordination. It is the backbone of Kubernetes, powering cluster state management at scale.
Supported versions
Available on
AWS
Azure
GCP
OCI
OpenShiftDatabases
MySQL
PostgreSQL
Oracle
SQL Server
Redis
ClickHouseVector & AI
Milvus
ElasticsearchMessage queues
KafkaOthers
etcd
ZooKeeperExtend database engines like plug-ins
KubeBlocks provides unified database operations through its addon-based architecture. With KubeBlocks Enterprise, access over 15 seamless integrations to scale your database services.
One control plane, consistent operations across all engines — powered by the addon mechanism.
Run etcd with guided lifecycle, scaling, observability, and recovery workflows
Operate etcd with a rich create wizard, dedicated compute and storage scaling dialogs, backup and restore workflows, live metrics, runtime logs, and task history evidence backed by real KubeBlocks Enterprise screenshots.

The create wizard keeps etcd deployment mode, compute, storage, backup, and environment choices visible before provisioning.
Create etcd clusters with mode, backup, and resource choices visible
Launch etcd from a guided create wizard that keeps deployment mode, engine version, environment, CPU and memory sizing, storage class, storage size, replicas, backup settings, maintenance window, and cluster summary visible before provisioning begins.
- Review the real etcd create wizard with both `Standalone` and `Cluster` deployment choices visible.
- Keep compute, storage, replicas, backup policy, and environment settings in the same workflow as version selection.
- Confirm the generated cluster summary before the deployment moves into day-2 operations.

Vertical Scaling shows etcd compute choices and execution timing before users save a resource change.

Volume Expansion keeps the storage class, current capacity, target capacity, and save action visible in one dialog.
Resize etcd compute and storage from dedicated dialogs
Vertical Scaling and Volume Expansion keep CPU, memory, and disk growth separate from generic task-state views, so users can review the actual change controls before submitting an operation.
- Use Vertical Scaling to compare etcd CPU and memory profiles before applying a compute update.
- Use Volume Expansion to review the storage class, current capacity, and target capacity before growing disks.
- Keep scaling evidence focused on pre-submit dialogs instead of post-submit task status.

The backups page keeps protection policy, repository context, and completed backup points visible from the etcd workspace.

The recovery flow turns an existing etcd backup into a guided restore path for rollback and validation.
Protect and recover etcd data with backup and restore workflows
Use the Backups page to review protection points and open Restore from an existing backup set when teams need rollback validation or safer maintenance windows.
- Review backup repository, policy, retention, and completed backup records from the etcd workspace.
- Open Restore from a real etcd backup set instead of recreating recovery inputs by hand.
- Keep backup and restore separate from lifecycle, scaling, and audit workflows.

Cluster Monitor gives teams a live view into etcd health and traffic behavior after the dashboard loads.

Runtime Log captures real etcd service output for troubleshooting and operational validation.
Track etcd health with metrics and runtime logs
Use Cluster Monitor to review service health, then pivot into Runtime Log when users need instance-level troubleshooting evidence without leaving the cluster workspace.
- Monitor etcd cluster status, members, traffic, and runtime signals from the live Metrics page after it hydrates.
- Inspect real Runtime Log output when validating startup, cluster-version updates, and service behavior.
- Keep observability separate from backup and audit workflows.

Task history gives teams a practical event trail for etcd provisioning and change review.
Trace etcd operations from task history
Task history records cluster events so teams can review who initiated an etcd change, when it ran, and whether it completed successfully before handing the service back to users.
- Review the event type, status, operation time, source, and user from one task timeline.
- Keep change review visible even when the fresh Tasks page does not yet contain day-2 records.
- Use task history as lightweight evidence for provisioning and change handoff.
Want full Day-2 operations on Kubernetes? Supported by KubeBlocks etcd Kubernetes Operator →
Ready to build your own DBaaS on Kubernetes?
Talk to our team and see how KubeBlocks Enterprise can help you consolidate databases, strengthen security, and reduce operational costs.

