Skip to content

[v1.40] Set VOLTRON_CA_SIGNER_NAME env var for certificate management#4674

Merged
rene-dekker merged 4 commits intotigera:release-v1.40from
rene-dekker:EV-6547-release-v1.40
Apr 13, 2026
Merged

[v1.40] Set VOLTRON_CA_SIGNER_NAME env var for certificate management#4674
rene-dekker merged 4 commits intotigera:release-v1.40from
rene-dekker:EV-6547-release-v1.40

Conversation

@rene-dekker
Copy link
Copy Markdown
Member

Summary

Operator now passes the CA certificate CommonName to Voltron via VOLTRON_CA_SIGNER_NAME, enabling configurable CA issuer identification.

Test plan

  • Unit test verifies VOLTRON_CA_SIGNER_NAME is set and non-empty when certificate management is enabled

🤖 Generated with Claude Code

rene-dekker and others added 3 commits April 10, 2026 14:58
…enabled

Passes the InstallationSpec CertificateManagement SignerName to the Voltron
container so it can identify the correct CA issuer public key, supporting
custom operator signer names (calico-private#11471).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
All Voltron env vars use the VOLTRON_ prefix to match envconfig processing.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Expose CACertCommonName() on the CertificateManager interface to provide
the parsed CN from the CA certificate. This is the actual value Voltron
needs to match against cert.Subject.CommonName in the trust bundle.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@rene-dekker rene-dekker merged commit a712ce4 into tigera:release-v1.40 Apr 13, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants