OCPBUGS-37706: allow TLS1.3 or modern profile to be specified

[sanchezl]

No description provided.

[openshift-ci-robot]

@sanchezl: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• c681774|allow TLS1.3 or modern profile to be specified: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@sanchezl: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 1caa9a8|allow TLS1.3 or modern profile to be specified: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[sanchezl]

/hold until all operators support tls 1.3

Known issues:

• etcd - OCPBUGS-43748: etcd pod containers do not start when tls min version is 1.3 cluster-etcd-operator#1364
• storage -

[openshift-ci-robot]

@sanchezl: This pull request references Jira Issue OCPBUGS-37706, which is invalid:

• expected the bug to target the "4.18.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In 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.

[wangke19]

/jira refresh

[openshift-ci-robot]

@wangke19: This pull request references Jira Issue OCPBUGS-37706, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.0) matches configured target version for branch (4.19.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @wangke19

In response to this:

/jira refresh

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.

[wangke19]

The PR has been pre-merge tested, got the expected results, detail see https://issues.redhat.com/browse/OCPBUGS-37706?focusedId=26306896&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-26306896

[wangke19]

/label qe-approved
/lgtm

[openshift-ci-robot]

@sanchezl: This pull request references Jira Issue OCPBUGS-37706, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.0) matches configured target version for branch (4.19.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @wangke19

In 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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS

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

[wangke19]

/test verify-commits

[sanchezl]

/hold cancel

[openshift-ci]

New changes are detected. LGTM label has been removed.

[openshift-ci-robot]

@sanchezl: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 2516160|UPSTREAM: : allow TLS1.3 or modern profile to be specified: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[sanchezl]

@wangke19 I had to rename the commit as per the conventions.

[wangke19]

/retest

[wangke19]

/retest

[gangwgr]

/retest

[gangwgr]

launch #2135

[gangwgr]

/test e2e-aws-ovn-serial

[openshift-ci]

@sanchezl: The following test 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/prow/e2e-aws-ovn-hypershift	2516160	link	true	/test e2e-aws-ovn-hypershift

Full PR test history. Your PR dashboard.

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.