Skip to content

ESO-417: Extends ExternalSecretsConfig with trustedCABundle for custom PKI#2011

Open
bharath-b-rh wants to merge 1 commit into
openshift:masterfrom
bharath-b-rh:eso-417
Open

ESO-417: Extends ExternalSecretsConfig with trustedCABundle for custom PKI#2011
bharath-b-rh wants to merge 1 commit into
openshift:masterfrom
bharath-b-rh:eso-417

Conversation

@bharath-b-rh
Copy link
Copy Markdown
Contributor

Summary

The enhancement proposal already described operand customization via ExternalSecretsConfig (for example global annotations, componentConfig / revisionHistoryLimit, and overrideEnv). This update extends that same proposal with spec.controllerConfig.trustedCABundle: optional ConfigMap-backed CA certificates for the external-secrets core controller TLS trust (alongside existing proxy/CNO behaviour), including validation, mount/SSL_CERT_DIR semantics, CEL interaction with overrideEnv, topology, tests, and support notes.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 14, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 14, 2026

@bharath-b-rh: This pull request references ESO-417 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

The enhancement proposal already described operand customization via ExternalSecretsConfig (for example global annotations, componentConfig / revisionHistoryLimit, and overrideEnv). This update extends that same proposal with spec.controllerConfig.trustedCABundle: optional ConfigMap-backed CA certificates for the external-secrets core controller TLS trust (alongside existing proxy/CNO behaviour), including validation, mount/SSL_CERT_DIR semantics, CEL interaction with overrideEnv, topology, tests, and support notes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot requested review from TrilokGeer and mytreya-rh May 14, 2026 15:52
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 14, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign trilokgeer for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

…m PKI

Signed-off-by: Bharath B <bhb@redhat.com>
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 15, 2026

@bharath-b-rh: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants