NO-JIRA: Add optional TLS scanner CI job for secrets-store-csi-driver-operator - #82718
NO-JIRA: Add optional TLS scanner CI job for secrets-store-csi-driver-operator#82718arun717 wants to merge 1 commit into
Conversation
Add a manually triggered tls-scanner presubmit on main that installs the operator via the Azure secrets-store CSI workflow and runs tls-scanner-run against openshift-cluster-csi-drivers.
WalkthroughThe CI configuration adds a ChangesTLS scanner CI integration
Estimated code review effort: 2 (Simple) | ~10 minutes Sequence Diagram(s)sequenceDiagram
participant tlsScannerJob as tls-scanner job
participant AzureWorkflow as Azure CSI workflow
participant CSIDriver as CSI driver
participant TLSScanner as TLS scanner tests
tlsScannerJob->>AzureWorkflow: Install operator bundle
AzureWorkflow->>CSIDriver: Configure readiness
tlsScannerJob->>TLSScanner: Run tls-13 and tls-scanner-run
Possibly related PRs
Important Pre-merge checks failedPlease resolve all errors before merging. Addressing warnings is optional. ❌ Failed checks (1 error)
✅ Passed checks (14 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: arun717 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@arun717: This pull request explicitly references no jira issue. 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. |
|
[REHEARSALNOTIFIER]
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals. Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse pull-ci-openshift-secrets-store-csi-driver-operator-main-tls-scanner |
|
@arun717: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@arun717: The following test 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. |
Summary
tls-scannerpresubmit foropenshift/secrets-store-csi-driver-operatoronmain.openshift-e2e-azure-csi-secrets-store, installs the operator via OLM intoopenshift-cluster-csi-drivers, enables TLS 1.3 strict adherence, and runstls-scanner-run.Test plan
/pj-rehearse listconfirmspull-ci-openshift-secrets-store-csi-driver-operator-main-tls-scanneris rehearsable/pj-rehearse pull-ci-openshift-secrets-store-csi-driver-operator-main-tls-scannersucceedsmain,/test tls-scannercan trigger the job after this mergesSummary by CodeRabbit
Adds an optional, manually triggered
tls-scannerpresubmit job foropenshift/secrets-store-csi-driver-operatoronmain.The job provisions an Azure cluster, installs the operator through OLM, enables strict TLS 1.3 adherence, and runs
tls-scanner-runwith configured scanner resources.