Skip to content

Move e2e-aws-ovn-tls-13 periodic jobs to nightly configs for releases 4.18-4.22#74257

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
wangke19:add-origin-tls13-job
Feb 4, 2026
Merged

Move e2e-aws-ovn-tls-13 periodic jobs to nightly configs for releases 4.18-4.22#74257
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
wangke19:add-origin-tls13-job

Conversation

@wangke19
Copy link
Contributor

@wangke19 wangke19 commented Feb 2, 2026

Summary

This PR moves TLS 1.3 (Modern profile) periodic test jobs from CI stream configs to nightly stream configs for OpenShift release versions 4.18, 4.19, 4.20, 4.21, and 4.22.

Changes

Removed from CI configs:

  • ci-operator/config/openshift/release/openshift-release-master__ci-4.18.yaml
  • ci-operator/config/openshift/release/openshift-release-master__ci-4.19.yaml

Added to nightly configs:

  • ci-operator/config/openshift/release/openshift-release-master__nightly-4.18.yaml
  • ci-operator/config/openshift/release/openshift-release-master__nightly-4.19.yaml
  • ci-operator/config/openshift/release/openshift-release-master__nightly-4.20.yaml
  • ci-operator/config/openshift/release/openshift-release-master__nightly-4.21.yaml
  • ci-operator/config/openshift/release/openshift-release-master__nightly-4.22.yaml

Generated:

  • ci-operator/jobs/openshift/release/openshift-release-master-periodics.yaml

Job Configuration

Each nightly periodic job:

  • Workflow: openshift-e2e-aws-ovn-tls-13
  • Test Suite: openshift/conformance/parallel
  • Interval: 168h (weekly)
  • Test Action: Patches API server to use TLS Modern profile (TLS 1.3) and runs conformance tests
  • Observers: observers-resource-watch enabled

Rationale: Why Nightly Instead of CI?

Components Impacted by TLS Security Profile Changes

The TLS 1.3 test modifies the API server's TLS security profile, which propagates to 8+ critical control plane components:

Core Control Plane:

  1. kube-apiserver
  2. kube-controller-manager
  3. kube-scheduler
  4. openshift-apiserver
  5. openshift-oauth-apiserver
  6. openshift-oauth-server
  7. etcd
  8. Machine Config Operator

Impact Analysis

Category Impact Level Details
Control Plane Security 🔴 HIGH Changes TLS config for all API servers and etcd
Authentication 🔴 HIGH OAuth server TLS directly affected
API Availability 🔴 HIGH Tests that APIs remain functional with Modern profile
Platform Stability 🟡 MEDIUM Runs wait-for-stable-cluster to verify rollout

Why Nightly Stream is More Appropriate

Security-Critical Testing

  • Modifies cluster-wide security settings affecting all client-server TLS handshakes
  • Changes authentication flows and etcd communications
  • Requires comprehensive validation against stable builds

Production-Oriented Testing

  • TLS profiles are deployment-time configurations, not code features
  • Should be tested against builds that will ship to customers (nightly stream)
  • Nightly builds are accepted, stable images closer to what customers use

Comprehensive Coverage

  • Nightly configs have ~189 tests vs CI's ~33 tests
  • After such significant security configuration changes, broader test coverage is essential
  • Aligns with how other security-focused tests (e.g., FIPS) are configured

Appropriate Test Scope

  • CI stream tests: Fast feedback for code changes (appropriate for feature development)
  • Nightly stream tests: Comprehensive validation of release payloads with various configurations (appropriate for deployment-time settings)

References

Testing

  • Verified workflow openshift-e2e-aws-ovn-tls-13 exists in step-registry
  • Ran make update to generate Prow job definitions
  • Generated periodic jobs in ci-operator/jobs/openshift/release/openshift-release-master-periodics.yaml

/assign @wangke19

@openshift-ci openshift-ci bot requested review from deads2k and sjenning February 2, 2026 13:42
@wangke19 wangke19 changed the title Add e2e-aws-ovn-tls-13 test job for origin main branch [WIP]Add e2e-aws-ovn-tls-13 test job for origin main branch Feb 2, 2026
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 2, 2026
@wangke19
Copy link
Contributor Author

wangke19 commented Feb 2, 2026

/pj-rehearse pull-ci-openshift-origin-main-e2e-aws-ovn-tls-13

@openshift-ci-robot
Copy link
Contributor

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

@wangke19
Copy link
Contributor Author

wangke19 commented Feb 3, 2026

e2e-aws-ovn-tls-13 is failed because openshift/origin#30746 has been merged.

@wangke19 wangke19 changed the title [WIP]Add e2e-aws-ovn-tls-13 test job for origin main branch Add e2e-aws-ovn-tls-13 test job for origin main branch Feb 3, 2026
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 3, 2026
@wangke19 wangke19 force-pushed the add-origin-tls13-job branch from 7f05982 to b5d10d4 Compare February 3, 2026 05:28
@wangke19 wangke19 changed the title Add e2e-aws-ovn-tls-13 test job for origin main branch Add e2e-aws-ovn-tls-13 periodic jobs for releases 4.20, 4.21, 4.22 Feb 3, 2026
This moves TLS 1.3 (Modern profile) periodic test jobs from CI stream
configs to nightly stream configs for OpenShift releases 4.18-4.22.

Rationale: The TLS 1.3 test modifies the API server's TLS security
profile, which propagates to 8+ critical control plane components:
- kube-apiserver, kube-controller-manager, kube-scheduler
- openshift-apiserver, openshift-oauth-apiserver, openshift-oauth-server
- etcd, Machine Config Operator

This is a high-risk, security-critical configuration change that:
1. Affects all API communications and authentication flows
2. Represents a deployment-time configuration (not code feature)
3. Should be tested against stable nightly builds, not pre-merge CI builds
4. Benefits from nightly's comprehensive test coverage (~189 vs ~33 tests)

Nightly stream testing is more appropriate for such cluster-wide security
configuration changes that impact production deployments.

Changes:
- Removed from: ci-operator/config/openshift/release/openshift-release-master__ci-4.{18,19}.yaml
- Added to: ci-operator/config/openshift/release/openshift-release-master__nightly-4.{18,19,20,21,22}.yaml
- Generated: ci-operator/jobs/openshift/release/openshift-release-master-periodics.yaml
@wangke19 wangke19 force-pushed the add-origin-tls13-job branch from b5d10d4 to b43769c Compare February 3, 2026 14:01
@wangke19 wangke19 changed the title Add e2e-aws-ovn-tls-13 periodic jobs for releases 4.20, 4.21, 4.22 Move e2e-aws-ovn-tls-13 periodic jobs to nightly configs for releases 4.18-4.22 Feb 3, 2026
@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@wangke19: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
periodic-ci-openshift-release-master-nightly-4.19-e2e-aws-ovn-tls-13 N/A periodic Periodic changed
periodic-ci-openshift-release-master-nightly-4.22-e2e-aws-ovn-tls-13 N/A periodic Periodic changed
periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-tls-13 N/A periodic Periodic changed
periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-tls-13 N/A periodic Periodic changed
periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-tls-13 N/A periodic Periodic changed
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.

@wangke19
Copy link
Contributor Author

wangke19 commented Feb 4, 2026

/pj-rehearse periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-tls-13

@openshift-ci-robot
Copy link
Contributor

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

@wangke19
Copy link
Contributor Author

wangke19 commented Feb 4, 2026

From failed CI job periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-tls-13, we saw,

: [sig-api-machinery][Feature:APIServer] TestTLSDefaults [Suite:openshift/conformance/parallel]

Reason: skip [github.com/openshift/origin/test/extended/apiserver/tls.go:126]: Cluster TLS profile is not default (intermediate), skipping cipher defaults check

That's expected, we need to openshift/origin#30746 merge.

@gangwgr
Copy link
Contributor

gangwgr commented Feb 4, 2026

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 4, 2026
@neisw
Copy link
Contributor

neisw commented Feb 4, 2026

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 4, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gangwgr, neisw, wangke19

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 4, 2026
@wangke19
Copy link
Contributor Author

wangke19 commented Feb 4, 2026

/pj-rehearse ack

@openshift-ci-robot
Copy link
Contributor

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

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Feb 4, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 4, 2026

@wangke19: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/rehearse/openshift/origin/main/e2e-aws-ovn-tls-13 7f05982 link unknown /pj-rehearse pull-ci-openshift-origin-main-e2e-aws-ovn-tls-13
ci/rehearse/periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-tls-13 b43769c link unknown /pj-rehearse periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-tls-13

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 69315f0 into openshift:master Feb 4, 2026
15 of 16 checks passed
@wangke19 wangke19 deleted the add-origin-tls13-job branch February 4, 2026 15:11
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