Skip to content

chore: set vault to 2.0 as default version#885

Merged
gboutry merged 1 commit into
canonical:mainfrom
gboutry:feat/vault-2.0
Jul 17, 2026
Merged

chore: set vault to 2.0 as default version#885
gboutry merged 1 commit into
canonical:mainfrom
gboutry:feat/vault-2.0

Conversation

@gboutry

@gboutry gboutry commented Jul 15, 2026

Copy link
Copy Markdown
Collaborator

This PR sets the default version of Vault to 2.0/stable, the supported LTS version of the 26.04 cycle.

QA steps

I've followed all these following documentations, and was able to successfully use secrets, vTPM, vTPM live migration (2026.1 new feature), and use tls certificates signed by Vault 2.0

https://canonical-openstack.readthedocs-hosted.com/en/latest/how-to/features/vault/
https://canonical-openstack.readthedocs-hosted.com/en/latest/how-to/features/secrets/
https://canonical-openstack.readthedocs-hosted.com/en/latest/how-to/misc/configuring-vtpm/
https://canonical-openstack.readthedocs-hosted.com/en/latest/how-to/features/managing-tls/tls-vault/

I have also tested refresh procedure on Vault on same track but different revisions.

Links

Jira card: OPEN-4629

@gboutry
gboutry requested review from Raven-182 and himax16 July 15, 2026 09:02
Set the default Vault channel to 2.0 and update upgrade-test fixtures
to use a supported manifest channel.

Assisted-By: Codex (gpt-5-5)
@gboutry
gboutry requested a review from ahmad-can July 16, 2026 07:59
@gboutry
gboutry merged commit c2335db into canonical:main Jul 17, 2026
6 checks passed
@gboutry
gboutry deleted the feat/vault-2.0 branch July 17, 2026 06:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants