OCPBUGS-78774: Add TLS Profile compliance#76
Conversation
|
@jmesnil: This pull request references Jira Issue OCPBUGS-78774, which is valid. 3 validation(s) were run on this bug
The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jmesnil The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Both the extractor (Rust) and exporter (Go) now fetch the TLS security profile from the API Server (apiservers.config.openshift.io/cluster) and apply it dynamically. Plain TCP and plain HTTP are removed entirely. Extractor: uses openssl crate with kube client to fetch the profile at startup. Exporter: fetches profile, maps OpenSSL cipher names to Go crypto/tls constants, serves HTTPS, connects to extractor over TLS with CA verification, and exits on profile change for pod restart. Manifests updated with TLS secret volume, CLI args, and RBAC for APIServer read access. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
f45cd9e to
7f12568
Compare
Force-add vcpkg test-data files that were excluded by .gitignore rules (*.dll, *.so, *.exe) to ensure complete vendor directory. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
@jmesnil: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
Both the extractor (Rust) and exporter (Go) now fetch the TLS security
profile from the API Server (apiservers.config.openshift.io/cluster)
and apply it dynamically. Plain TCP and plain HTTP are removed entirely.
Extractor: uses openssl crate with kube client to fetch the profile at
startup. Exporter: fetches profile, maps OpenSSL cipher names to Go
crypto/tls constants, serves HTTPS, connects to extractor over TLS with
CA verification, and exits on profile change for pod restart.
Manifests updated with TLS secret volume, CLI args, and RBAC for
APIServer read access.