Charmed Etcd is generally available!

Hello :wave:

We are happy to announce the first generally available release of Charmed etcd, now published in the 3.6/stable charmhub track for the IaaS / VM flavour!

Charm Version Charm channel Sources (github) License
Charmed etcd 3.6.5 3.6/stable
(r119: amd64, r120: arm64)
charmed-etcd-operator Apache 2.0

Release notes can be found here.

Available Features:

Supported features

  • High Availability
    • Scaling a cluster up and down, safely
    • automated rolling operations (restarts, certificates rotation, restore etc)
    • Recovery from majority failure
    • Persistent Storage management and reuse
  • Backup and restore
    • Integration with any AWS S3-compatible or Azure object storage
  • Authentication and authorisation by default
    • Automated user and permission management for client applications
    • Juju user secrets for charm internal passwords
  • TLS encryption
    • Peer-to-peer
    • Client
    • Automated certificate and CA rotation
    • mTLS for client applications
    • Juju secrets for private keys management
  • Minor version upgrades (without downtime)
  • External client relations (with mTLS)
  • Advanced statuses (multiple juju statuses reported via action)
  • Observability with Canonical Observability Stack (COS)
  • Tuning of configuration settings:
    • election-timeout
    • heartbeat-interval
    • quota-backend-bytes
    • certificate-extra-sans
    • client/peer-certificate-domain
  • AMD64 and ARM64 support
  • Automated deployment on VM
    • Terraform charm module
    • Terraform product module
    • Terraform solution module for Azure and AWS

Documentation can be found here.

Inside the charms:

  • etcd: 3.6.5

Artifacts:

In addition to our charms, we also released to 3.6/stable other artifacts, namely:

Artifact Version Sources (github) License
Snap: Charmed etcd 3.6.5 charmed-etcd-snap Apache 2.0
Rock: Charmed etcd 3.6.5 charmed-etcd-rock Apache 2.0

How to reach the team:

Chat with us about your use case on Matrix. Reach the commercial team here.

Bug reports may be filed on GitHub. We also welcome contributions to our documentation and to our projects.

Recognition:

Great work and big thanks to the team: @reneradoi @skourta. To @avgomes for all her work in the documentation, as well as to the rest of the extended team that made this release possible. This release would not have happened but for your dedication and hard work.

4 Likes