Skip to content

feat: support supplemental bundle path for vault upstream authority#6616

Closed
heybronson wants to merge 2 commits intospiffe:mainfrom
heybronson:heybronson/supplemental-vault
Closed

feat: support supplemental bundle path for vault upstream authority#6616
heybronson wants to merge 2 commits intospiffe:mainfrom
heybronson:heybronson/supplemental-vault

Conversation

@heybronson
Copy link
Copy Markdown

@heybronson heybronson commented Jan 29, 2026

Pull Request check list

  • Commit conforms to CONTRIBUTING.md?
  • Proper tests/regressions included?
  • Documentation updated?

Affected functionality

Vault upstream authority plugin

Description of change

This PR adds supplemental_bundle_path support to the Vault upstream authority plugin, enabling graceful root CA rotation.

Currently, the Vault plugin only includes the current root CA in the trust bundle. When the root CA rotates, workloads with certificates signed by the old root can no longer validate because the old root is immediately replaced. This makes root CA rotation disruptive.

The new supplemental_bundle_path configuration option allows operators to specify a PEM file containing additional root CA certificates to include in the trust bundle. This mirrors the existing implementation in the AWS PCA upstream authority plugin.

Which issue this PR fixes

related to: #5101

@sorindumitru
Copy link
Copy Markdown
Collaborator

Currently, the Vault plugin only includes the current root CA in the trust bundle. When the root CA rotates, workloads with certificates signed by the old root can no longer validate because the old root is immediately replaced. This makes root CA rotation disruptive.

Did you actually notice this behaviour in practice? The old CA shouldn't be removed immediately, it should still stay in the bundle while it is in use and for at least 24h after that.

@sorindumitru
Copy link
Copy Markdown
Collaborator

Hi @heybronson, just checking in if you had some time to look at this comment

@sorindumitru
Copy link
Copy Markdown
Collaborator

@heybronson , we'll close this for now, if you're still interested in this, please reopen.

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.

2 participants