• Logo
    Vault Charms
  • github.com/canonical/vault-k8s-operator
  • More resources
    • Discourse
    • Matrix
    • GitHub
Contents Menu Expand Light mode Dark mode Auto light/dark, in light mode Auto light/dark, in dark mode Skip to content
Vault Charms documentation
Vault Charms documentation
  • Tutorials
    • Getting Started (Kubernetes)
    • Getting Started (Machine)
  • How-to guides
    • Unseal a sealed unit (K8s)
    • Unseal a sealed unit (Machine)
    • Use Vault behind an Ingress (K8s)
    • Use Vault behind an Ingress (Machine)
    • Use Vault as an intermediate CA
    • Use Vault as an ACME Server to obtain TLS certificates
    • Integrate with COS (K8s)
    • Integrate with COS (Machine)
    • Configure a Vault for auto-unseal
    • Scale (K8s)
    • Scale (Machine)
    • Create a backup
    • Restore a backup
    • Upgrade Vault
    • Upgrade from 1.1x to 2.0
    • Recover a Vault Cluster When Raft Quorum is Lost
  • Reference
    • Storage Backend
    • TLS
    • Unsealing
    • Production blueprint (k8s)
    • Production blueprint (machine)
    • S3 storage for Backup and Restore
    • Key differences between Vault charm version 1.8 and 1.15
    • Relation-based secret engines
    • Charm Policies
    • Release Notes
    • Supported Releases
  • Explanation
    • High Availability
    • Security
Back to top

Release Notes¶

Vault 2.0¶

What’s New¶

  • Upgraded Vault workload from 1.19 to 2.0

  • Updated certificate transfer library to use charmlibs interface

Upgrade Path¶

See the upgrade from 1.1x to 2.0 guide for step-by-step instructions.

Full Changelog: Changes compared to 1.19

© 2026 CC-BY-SA, Canonical Ltd.
Last updated on May 28, 2026
Contents
  • Release Notes
    • Vault 2.0
      • What’s New
      • Upgrade Path