Skip to content

Add TLS PQC compliance and TLS 1.3 adherence tests for OADP operator - #79196

Merged
openshift-merge-bot[bot] merged 3 commits into
openshift:mainfrom
Joeavaikath:oadp-tls-pqc-compliance
May 18, 2026
Merged

Add TLS PQC compliance and TLS 1.3 adherence tests for OADP operator#79196
openshift-merge-bot[bot] merged 3 commits into
openshift:mainfrom
Joeavaikath:oadp-tls-pqc-compliance

Conversation

@Joeavaikath

@Joeavaikath Joeavaikath commented May 12, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add TLS PQC readiness and TLS 1.3 adherence CI tests for the OADP operator on oadp-dev and oadp-1.6 branches (4.22 OCP variant)
  • Each test uses the optional-operators-ci-aws workflow to provision a cluster and install OADP via OLM, then configures the TLS 1.3 Modern profile (tls-13 step) and runs the tls-scanner-run step scoped to the openshift-adp namespace
  • Available as optional PR-triggered tests (/test 4.22-tls-pqc-readiness, /test 4.22-tls13-adherence) and weekly periodic jobs (Mondays 06:00 UTC)

Test plan

  • Rehearsal jobs pass for the new test definitions
  • Trigger /test 4.22-tls-pqc-readiness on the PR to validate the PQC readiness scan
  • Trigger /test 4.22-tls13-adherence on the PR to validate the TLS 1.3 adherence scan

This PR updates OpenShift CI configuration for the OADP operator (oadp-dev and oadp-1.6 branches, 4.22 variant) to add automated TLS compliance testing using the tls-scanner-tool.

What changed (practical impact)

  • Adds a tls-scanner-tool base image entry (ocp:4.22, tag tls-scanner-tool) to CI base_images.
  • Introduces two TLS-focused test suites on both branches:
    • tls-pqc-readiness — PQC readiness scan (PQC_CHECK: "true")
    • tls13-adherence — TLS 1.3 adherence scan (PQC_CHECK: "false", TLS_13_ENABLE_TLS_ADHERENCE: "true", TLS_13_TLS_ADHERENCE_POLICY: StrictAllComponents)
  • Each suite is available as:
    • an optional PR-triggered job (/test 4.22-tls-pqc-readiness and /test 4.22-tls13-adherence) that provisions a cluster via the optional-operators-ci-operator-sdk-aws workflow, installs OADP via OLM, enables the TLS 1.3 Modern profile (tls-13 step), and runs the tls-scanner-run ref scoped to the openshift-adp namespace.
    • a weekly periodic job scheduled Mondays at 06:00 UTC (cron: 0 6 * * 1).
  • Tests set OO_INSTALL_MODE=OwnNamespace, OO_INSTALL_NAMESPACE=openshift-adp, SCAN_NAMESPACE=openshift-adp, and SCANNER_CPU="2" (reduced to 2 cores to help scheduling).
  • The operator bundle is built as oadp-operator-bundle (build/Dockerfile.bundle) with skip_building_index: true — the TLS scanner tests were migrated from the deprecated OO_INDEX flow to the operator-sdk bundle workflow.

Test plan / verification

  • Rehearsal jobs must pass; the author ran /pj-rehearse and specific rehearsal commands for the new jobs.
  • Validate by triggering the PR jobs: /test 4.22-tls-pqc-readiness and /test 4.22-tls13-adherence.

Files affected

  • ci-operator/config/openshift/oadp-operator/openshift-oadp-operator-oadp-1.6__4.22.yaml
  • ci-operator/config/openshift/oadp-operator/openshift-oadp-operator-oadp-dev__4.22.yaml

Notes and reviewer context

@coderabbitai

coderabbitai Bot commented May 12, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (6)
  • ci-operator/jobs/openshift/oadp-operator/openshift-oadp-operator-oadp-1.6-periodics.yaml is excluded by !ci-operator/jobs/**
  • ci-operator/jobs/openshift/oadp-operator/openshift-oadp-operator-oadp-1.6-postsubmits.yaml is excluded by !ci-operator/jobs/**
  • ci-operator/jobs/openshift/oadp-operator/openshift-oadp-operator-oadp-1.6-presubmits.yaml is excluded by !ci-operator/jobs/**
  • ci-operator/jobs/openshift/oadp-operator/openshift-oadp-operator-oadp-dev-periodics.yaml is excluded by !ci-operator/jobs/**
  • ci-operator/jobs/openshift/oadp-operator/openshift-oadp-operator-oadp-dev-postsubmits.yaml is excluded by !ci-operator/jobs/**
  • ci-operator/jobs/openshift/oadp-operator/openshift-oadp-operator-oadp-dev-presubmits.yaml is excluded by !ci-operator/jobs/**

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: bc86b143-ab0b-4ba2-9d04-d449668c98da

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Walkthrough

Adds a tls-scanner-tool base image and four TLS scanning CI jobs (tls-pqc-readiness, tls-pqc-readiness-periodic, tls13-adherence, tls13-adherence-periodic) to the OADP operator ci-operator configs for 1.6 and dev on OpenShift 4.22; periodic variants run weekly via cron.

Changes

TLS scanning CI additions

Layer / File(s) Summary
Base image declaration
ci-operator/config/openshift/oadp-operator/openshift-oadp-operator-oadp-1.6__4.22.yaml, ci-operator/config/openshift/oadp-operator/openshift-oadp-operator-oadp-dev__4.22.yaml
Adds base_images.tls-scanner-tool with name: "4.22", namespace: ocp, tag: tls-scanner-tool.
Operator bundle build target
ci-operator/config/openshift/oadp-operator/...-oadp-1.6__4.22.yaml, ...-oadp-dev__4.22.yaml
Adds a bundle build entry as: oadp-operator-bundle using build/Dockerfile.bundle and skip_building_index: true.
Optional TLS scanner jobs (non-periodic)
ci-operator/config/openshift/oadp-operator/...-oadp-1.6__4.22.yaml, ...-oadp-dev__4.22.yaml
Adds tls-pqc-readiness and tls13-adherence jobs using workflow: optional-operators-ci-operator-sdk-aws, refs: [tls-13, tls-scanner-run], OO_BUNDLE: oadp-operator-bundle, OO_INSTALL_MODE: OwnNamespace, OO_INSTALL_NAMESPACE: openshift-adp, SCAN_NAMESPACE: openshift-adp, SCANNER_CPU: "2". tls-pqc-readiness sets PQC_CHECK: "true". tls13-adherence sets PQC_CHECK: "false", TLS_13_ENABLE_TLS_ADHERENCE: "true", TLS_13_TLS_ADHERENCE_POLICY: StrictAllComponents.
Periodic TLS scanner jobs
ci-operator/config/openshift/oadp-operator/...-oadp-1.6__4.22.yaml, ...-oadp-dev__4.22.yaml
Adds tls-pqc-readiness-periodic and tls13-adherence-periodic with the same env and refs as their non-periodic counterparts and cron: 0 6 * * 1 for weekly execution.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested labels

lgtm, rehearsals-ack

🚥 Pre-merge checks | ✅ 12
✅ Passed checks (12 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly and accurately describes the main changes: adding TLS PQC compliance and TLS 1.3 adherence tests to the OADP operator CI configuration.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed PR modifies YAML CI config files only, no Ginkgo test files. Check for stable test names is not applicable to YAML configuration.
Test Structure And Quality ✅ Passed Check targets Ginkgo test code (.go files). PR contains only YAML CI configuration changes—no test code present. Check not applicable.
Microshift Test Compatibility ✅ Passed The PR modifies only CI configuration YAML files in openshift/release, not new Ginkgo test code. The check applies to new e2e tests with It(), Describe(), etc., which are not present here.
Single Node Openshift (Sno) Test Compatibility ✅ Passed No Ginkgo e2e tests are added in this PR. Changes only add CI job definitions (YAML config) that reference existing shell-script test steps. The custom check applies only to new Ginkgo tests.
Topology-Aware Scheduling Compatibility ✅ Passed Modified files are CI configuration (ci-operator/config/) defining test workflows and environment variables, not deployment manifests, operator code, or controllers. Check scope does not apply.
Ote Binary Stdout Contract ✅ Passed This PR modifies YAML CI configuration files only. The OTE Binary Stdout Contract check applies to executable source code, not declarative configuration files.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR adds CI test configuration (YAML) only, not Ginkgo test code. Referenced test steps contain no IPv4 assumptions or external connectivity requirements. Check not applicable.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


Comment @coderabbitai help to get the list of available commands and usage tips.

@Joeavaikath

Copy link
Copy Markdown
Contributor Author

/pj-rehearse

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@Joeavaikath: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@Joeavaikath

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-oadp-operator-oadp-1.6-4.22-tls-pqc-readiness

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@Joeavaikath: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@Joeavaikath

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-oadp-operator-oadp-dev-4.22-tls13-adherence-periodic

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@Joeavaikath: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@Joeavaikath

Copy link
Copy Markdown
Contributor Author

/pj-rehearse

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@Joeavaikath: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@weshayutin weshayutin left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/LGTM

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 13, 2026
@kaovilai

Copy link
Copy Markdown
Member

keep in mind #79152 in the middle of migrating away from optional-operators-ci-aws

@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label May 13, 2026
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 13, 2026
@openshift-ci openshift-ci Bot added lgtm Indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed lgtm Indicates that a PR is ready to be merged. labels May 13, 2026
@Joeavaikath
Joeavaikath force-pushed the oadp-tls-pqc-compliance branch from 0c39701 to 9772e0c Compare May 13, 2026 19:04
@openshift-ci openshift-ci Bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 13, 2026
@Joeavaikath

Copy link
Copy Markdown
Contributor Author

/pj-rehearse

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@Joeavaikath: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci openshift-ci Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 13, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@Joeavaikath, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

couldn't prepare candidate: couldn't rebase candidate onto 825e7789afc870524d3b8077258cf307ff9947ea due to conflicts
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

Adds tls-pqc-readiness and tls13-adherence tests to oadp-dev and
oadp-1.6 branch CI on the 4.22 OCP variant. Each test installs OADP
via OLM, configures the TLS 1.3 Modern profile, then runs the
tls-scanner scoped to the openshift-adp namespace. Available as
optional PR tests and weekly periodic jobs (Mondays 06:00 UTC).

Signed-off-by: Joseph <jvaikath@redhat.com>
Signed-off-by: Joseph <jvaikath@redhat.com>
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@Joeavaikath: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@kaovilai

Copy link
Copy Markdown
Member

/pj-rehearse pull-ci-openshift-oadp-operator-oadp-1.6-4.22-tls-pqc-readiness pull-ci-openshift-oadp-operator-oadp-1.6-4.22-tls13-adherence pull-ci-openshift-oadp-operator-oadp-1.6-4.22-ci-index pull-ci-openshift-oadp-operator-oadp-1.6-4.22-e2e-test-aws pull-ci-openshift-oadp-operator-oadp-1.6-4.22-e2e-test-cli-aws pull-ci-openshift-oadp-operator-oadp-1.6-4.22-e2e-test-hcp-aws pull-ci-openshift-oadp-operator-oadp-1.6-4.22-e2e-test-kubevirt-aws pull-ci-openshift-oadp-operator-oadp-1.6-4.22-images periodic-ci-openshift-oadp-operator-oadp-1.6-4.22-e2e-test-kubevirt-aws-periodic periodic-ci-openshift-oadp-operator-oadp-1.6-4.22-e2e-test-hcp-aws-periodic periodic-ci-openshift-oadp-operator-oadp-1.6-4.22-tls-pqc-readiness-periodic periodic-ci-openshift-oadp-operator-oadp-1.6-4.22-tls13-adherence-periodic periodic-ci-openshift-oadp-operator-oadp-1.6-4.22-e2e-test-aws-periodic periodic-ci-openshift-oadp-operator-oadp-1.6-4.22-e2e-test-cli-aws-periodic

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@kaovilai: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@Joeavaikath

Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-oadp-operator-oadp-dev-4.22-tls13-adherence-periodic periodic-ci-openshift-oadp-operator-oadp-1.6-4.22-e2e-test-aws-periodic periodic-ci-openshift-oadp-operator-oadp-1.6-4.22-e2e-test-cli-aws-periodic

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@Joeavaikath: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@kaovilai

Copy link
Copy Markdown
Member

/lgtm
/unhold

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 18, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 18, 2026
@openshift-ci

openshift-ci Bot commented May 18, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Joeavaikath, kaovilai, shubham-pampattiwar, weshayutin

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

The pull request process is described 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

@kaovilai

Copy link
Copy Markdown
Member

/pj-rehearse ack

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@kaovilai: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label May 18, 2026
@openshift-merge-bot
openshift-merge-bot Bot merged commit 8faa1be into openshift:main May 18, 2026
31 checks passed
@weshayutin

weshayutin commented May 19, 2026

Copy link
Copy Markdown
Contributor

OADP-6073

wgahnagl pushed a commit to wgahnagl/release that referenced this pull request May 20, 2026
…penshift#79196)

* Add TLS PQC compliance and TLS 1.3 adherence tests for OADP operator

Adds tls-pqc-readiness and tls13-adherence tests to oadp-dev and
oadp-1.6 branch CI on the 4.22 OCP variant. Each test installs OADP
via OLM, configures the TLS 1.3 Modern profile, then runs the
tls-scanner scoped to the openshift-adp namespace. Available as
optional PR tests and weekly periodic jobs (Mondays 06:00 UTC).

Signed-off-by: Joseph <jvaikath@redhat.com>

* CPU count to 2

Signed-off-by: Joseph <jvaikath@redhat.com>

* Regenerate Prow jobs for oadp-dev and oadp-1.6 4.22 variants

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Joseph <jvaikath@redhat.com>

---------

Signed-off-by: Joseph <jvaikath@redhat.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
andrej1991 pushed a commit to andrej1991/release that referenced this pull request Jul 6, 2026
…penshift#79196)

* Add TLS PQC compliance and TLS 1.3 adherence tests for OADP operator

Adds tls-pqc-readiness and tls13-adherence tests to oadp-dev and
oadp-1.6 branch CI on the 4.22 OCP variant. Each test installs OADP
via OLM, configures the TLS 1.3 Modern profile, then runs the
tls-scanner scoped to the openshift-adp namespace. Available as
optional PR tests and weekly periodic jobs (Mondays 06:00 UTC).

Signed-off-by: Joseph <jvaikath@redhat.com>

* CPU count to 2

Signed-off-by: Joseph <jvaikath@redhat.com>

* Regenerate Prow jobs for oadp-dev and oadp-1.6 4.22 variants

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Joseph <jvaikath@redhat.com>

---------

Signed-off-by: Joseph <jvaikath@redhat.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
TimurMP pushed a commit to TimurMP/release that referenced this pull request Jul 8, 2026
…penshift#79196)

* Add TLS PQC compliance and TLS 1.3 adherence tests for OADP operator

Adds tls-pqc-readiness and tls13-adherence tests to oadp-dev and
oadp-1.6 branch CI on the 4.22 OCP variant. Each test installs OADP
via OLM, configures the TLS 1.3 Modern profile, then runs the
tls-scanner scoped to the openshift-adp namespace. Available as
optional PR tests and weekly periodic jobs (Mondays 06:00 UTC).

Signed-off-by: Joseph <jvaikath@redhat.com>

* CPU count to 2

Signed-off-by: Joseph <jvaikath@redhat.com>

* Regenerate Prow jobs for oadp-dev and oadp-1.6 4.22 variants

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Joseph <jvaikath@redhat.com>

---------

Signed-off-by: Joseph <jvaikath@redhat.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
SachinNinganure pushed a commit to SachinNinganure/release that referenced this pull request Jul 20, 2026
…penshift#79196)

* Add TLS PQC compliance and TLS 1.3 adherence tests for OADP operator

Adds tls-pqc-readiness and tls13-adherence tests to oadp-dev and
oadp-1.6 branch CI on the 4.22 OCP variant. Each test installs OADP
via OLM, configures the TLS 1.3 Modern profile, then runs the
tls-scanner scoped to the openshift-adp namespace. Available as
optional PR tests and weekly periodic jobs (Mondays 06:00 UTC).

Signed-off-by: Joseph <jvaikath@redhat.com>

* CPU count to 2

Signed-off-by: Joseph <jvaikath@redhat.com>

* Regenerate Prow jobs for oadp-dev and oadp-1.6 4.22 variants

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Joseph <jvaikath@redhat.com>

---------

Signed-off-by: Joseph <jvaikath@redhat.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
jzding added a commit to jzding/release that referenced this pull request Jul 27, 2026
Add TLS compliance scanning to PTP operator CI per OCPSTRAT-2611,
following the patterns from OADP (PR openshift#79196) and gcp-filestore
(PR openshift#81917).

For each branch (release-4.22, release-4.23), add:

Presubmit (on-demand, optional, non-blocking):
- tls-pqc-readiness: deploys PTP operator via OLM (ci-index), runs
  tls-13 step then tls-scanner-run with PQC check enabled
- tls13-adherence: same flow with TLS 1.3 StrictAllComponents
  adherence policy

Periodic (weekly Monday 6am UTC):
- tls-pqc-readiness-periodic: same as presubmit PQC test
- tls13-adherence-periodic: same as presubmit adherence test

All tests:
- Use optional-operators-ci-aws workflow (deploys PTP from ci-index)
- Scoped to openshift-ptp namespace via SCAN_NAMESPACE
- Use tls-scanner-tool from the tls-scanner namespace (official image)

Branches 5.0/5.1/main are skipped because the PTP operator CSV is
not yet available in the standard catalog for those versions.
linuxptp-daemon is skipped because it has no operator bundle config.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Jack Ding <jackding@gmail.com>
jzding added a commit to jzding/release that referenced this pull request Jul 27, 2026
Add TLS compliance scanning to PTP operator CI per OCPSTRAT-2611,
following the patterns from OADP (PR openshift#79196) and gcp-filestore
(PR openshift#81917).

For each branch (4.22, 4.23, 5.0, 5.1, main), add a combined
tls-scan test that covers both TLS 1.3 adherence (StrictAllComponents)
and PQC readiness in a single cluster deploy:

Presubmit (on-demand):
- tls-scan: always_run false, optional true. Deploys PTP operator
  via ci-index, runs tls-13 then tls-scanner-run with PQC check and
  TLS 1.3 StrictAllComponents adherence enabled.

Periodic (weekly, staggered):
- tls-scan-periodic: 4.22 Saturday, 4.23 Monday, 5.0 Tuesday,
  5.1 Wednesday, main Thursday (all 6am UTC).

All tests use optional-operators-ci-aws workflow, scoped to
openshift-ptp namespace, SCANNER_CPU=2, tls-scanner-tool from
the official tls-scanner namespace.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Jack Ding <jackding@gmail.com>
jzding added a commit to jzding/release that referenced this pull request Jul 27, 2026
Add TLS compliance scanning to PTP operator CI per OCPSTRAT-2611,
following the patterns from OADP (PR openshift#79196) and gcp-filestore
(PR openshift#81917).

For each branch (4.22, 4.23, 5.0, 5.1, main), add a combined
tls-scan test that covers both TLS 1.3 adherence (StrictAllComponents)
and PQC readiness in a single cluster deploy:

Presubmit (on-demand):
- tls-scan: always_run false, optional true. Deploys PTP operator
  via ci-index, runs tls-13 then tls-scanner-run with PQC check and
  TLS 1.3 StrictAllComponents adherence enabled.

Periodic (weekly Saturday, staggered 3 hours):
- 4.22 at 00:00 UTC, 4.23 at 03:00, 5.0 at 06:00,
  5.1 at 09:00, main at 12:00.

All tests use optional-operators-ci-aws workflow, scoped to
openshift-ptp namespace, SCANNER_CPU=2, tls-scanner-tool from
the official tls-scanner namespace.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Jack Ding <jackding@gmail.com>
jzding added a commit to jzding/release that referenced this pull request Jul 27, 2026
Add TLS compliance scanning to PTP operator CI per OCPSTRAT-2611,
following the patterns from OADP (PR openshift#79196) and gcp-filestore
(PR openshift#81917).

For each branch (4.22, 4.23, 5.0, 5.1, main), add a combined
tls-scan test that covers both TLS 1.3 adherence (StrictAllComponents)
and PQC readiness in a single cluster deploy:

Presubmit (on-demand):
- tls-scan: always_run false, optional true. Deploys PTP operator
  via ci-index, runs tls-13 then tls-scanner-run with PQC check and
  TLS 1.3 StrictAllComponents adherence enabled.

Periodic (weekly Saturday, staggered 3 hours):
- 4.22 at 00:00 UTC, 4.23 at 03:00, 5.0 at 06:00,
  5.1 at 09:00, main at 12:00.

All tests use optional-operators-ci-aws workflow, scoped to
openshift-ptp namespace, SCANNER_CPU=2, tls-scanner-tool from
the official tls-scanner namespace.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Jack Ding <jackding@gmail.com>
jzding added a commit to jzding/release that referenced this pull request Jul 28, 2026
Add TLS compliance scanning to PTP operator CI per OCPSTRAT-2611,
following the patterns from OADP (PR openshift#79196) and gcp-filestore
(PR openshift#81917).

For each branch (4.22, 4.23, 5.0, 5.1, main), add a combined
tls-scan test that covers both TLS 1.3 adherence (StrictAllComponents)
and PQC readiness in a single cluster deploy:

Presubmit (on-demand):
- tls-scan: always_run false, optional true. Deploys PTP operator
  via ci-index, runs tls-13, waits for PTP operator to restart with
  the new TLS profile, then runs tls-scanner-run.

The wait-ptp-tls-restart step is needed because the PTP operator's
SecurityProfileWatcher detects the TLS profile change from the tls-13
step and self-terminates for OLM to restart it. The reconciler then
re-renders the kube-rbac-proxy daemonset template with the new TLS
min version and cipher suites. Without the wait, the scanner would
scan endpoints still running with the old TLS configuration.

Periodic (weekly Saturday, staggered 3 hours):
- 4.22 at 00:00 UTC, 4.23 at 03:00, 5.0 at 06:00,
  5.1 at 09:00, main at 12:00.

All tests use optional-operators-ci-aws workflow, scoped to
openshift-ptp namespace, SCANNER_CPU=2, tls-scanner-tool from
the official tls-scanner namespace.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Jack Ding <jackding@gmail.com>
jzding added a commit to jzding/release that referenced this pull request Jul 28, 2026
Add TLS compliance scanning to PTP operator CI per OCPSTRAT-2611,
following the patterns from OADP (PR openshift#79196) and gcp-filestore
(PR openshift#81917).

For each branch (4.22, 4.23, 5.0, 5.1, main), add a combined
tls-scan test that covers both TLS 1.3 adherence (StrictAllComponents)
and PQC readiness in a single cluster deploy:

Presubmit (on-demand):
- tls-scan: always_run false, optional true. Deploys PTP operator
  via ci-index, runs tls-13, waits for PTP operator to restart with
  the new TLS profile, then runs tls-scanner-run.

The wait-ptp-tls-restart step is needed because the PTP operator's
SecurityProfileWatcher detects the TLS profile change from the tls-13
step and self-terminates for OLM to restart it. The reconciler then
re-renders the kube-rbac-proxy daemonset template with the new TLS
min version and cipher suites. Without the wait, the scanner would
scan endpoints still running with the old TLS configuration.

Periodic (weekly Saturday, staggered 3 hours):
- 4.22 at 00:00 UTC, 4.23 at 03:00, 5.0 at 06:00,
  5.1 at 09:00, main at 12:00.

All tests use optional-operators-ci-aws workflow, scoped to
openshift-ptp namespace, SCANNER_CPU=2, tls-scanner-tool from
the official tls-scanner namespace.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Jack Ding <jackding@gmail.com>
jzding added a commit to jzding/release that referenced this pull request Jul 28, 2026
Add TLS compliance scanning to PTP operator CI per OCPSTRAT-2611,
following the patterns from OADP (PR openshift#79196) and gcp-filestore
(PR openshift#81917).

For each branch (4.22, 4.23, 5.0, 5.1, main), add a combined
tls-scan test that covers both TLS 1.3 adherence (StrictAllComponents)
and PQC readiness in a single cluster deploy:

Presubmit (on-demand):
- tls-scan: always_run false, optional true. Deploys PTP operator
  via ci-index, runs tls-13, waits for PTP operator to restart with
  the new TLS profile, then runs tls-scanner-run.

The wait-ptp-tls-restart step is needed because the PTP operator's
SecurityProfileWatcher detects the TLS profile change from the tls-13
step and self-terminates for OLM to restart it. The reconciler then
re-renders the kube-rbac-proxy daemonset template with the new TLS
min version and cipher suites. Without the wait, the scanner would
scan endpoints still running with the old TLS configuration.

Periodic (weekly Saturday, staggered 3 hours):
- 4.22 at 00:00 UTC, 4.23 at 03:00, 5.0 at 06:00,
  5.1 at 09:00, main at 12:00.

All tests use optional-operators-ci-aws workflow, scoped to
openshift-ptp namespace, SCANNER_CPU=2, tls-scanner-tool from
the official tls-scanner namespace.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Jack Ding <jackding@gmail.com>
jzding added a commit to jzding/release that referenced this pull request Jul 28, 2026
Add TLS compliance scanning to PTP operator CI per OCPSTRAT-2611,
following the patterns from OADP (PR openshift#79196) and gcp-filestore
(PR openshift#81917).

For each branch (4.22, 4.23, 5.0, 5.1, main), add a combined
tls-scan test that covers both TLS 1.3 adherence (StrictAllComponents)
and PQC readiness in a single cluster deploy:

Presubmit (on-demand):
- tls-scan: always_run false, optional true. Deploys PTP operator
  via ci-index, runs tls-13, waits for PTP operator to restart with
  the new TLS profile, then runs tls-scanner-run.

The wait-ptp-tls-restart step is needed because the PTP operator's
SecurityProfileWatcher detects the TLS profile change from the tls-13
step and self-terminates for OLM to restart it. The reconciler then
re-renders the kube-rbac-proxy daemonset template with the new TLS
min version and cipher suites. Without the wait, the scanner would
scan endpoints still running with the old TLS configuration.

Periodic (weekly Saturday, staggered 3 hours):
- 4.22 at 00:00 UTC, 4.23 at 03:00, 5.0 at 06:00,
  5.1 at 09:00, main at 12:00.

All tests use optional-operators-ci-aws workflow, scoped to
openshift-ptp namespace, SCANNER_CPU=2, tls-scanner-tool from
the official tls-scanner namespace.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Signed-off-by: Jack Ding <jackding@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants