Skip to content

Conversation

@jmencak
Copy link
Contributor

@jmencak jmencak commented Apr 30, 2025

Set the minimum default version to TLS 1.3. PQ algorithms will only be supported in TLS 1.3+. Hybrid key agreements for TLS 1.3 X25519MLKEM768 is automatically supported by default in go 1.24.

See: OCPSTRAT-1858

Set the minimum default version to TLS 1.3.  PQ algorithms will only be
supported in TLS 1.3+.  Hybrid key agreements for TLS 1.3 X25519MLKEM768
is automatically supported by default in go 1.24.

See: OCPSTRAT-1858
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 30, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Apr 30, 2025

@jmencak: This pull request explicitly references no jira issue.

In response to this:

Set the minimum default version to TLS 1.3. PQ algorithms will only be supported in TLS 1.3+. Hybrid key agreements for TLS 1.3 X25519MLKEM768 is automatically supported by default in go 1.24.

See: OCPSTRAT-1858

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 openshift-ci bot requested review from ffromani and rbaturov April 30, 2025 06:39
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 30, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jmencak

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

The pull request process is described here

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 Apr 30, 2025
@jmencak
Copy link
Contributor Author

jmencak commented Apr 30, 2025

Infra issues
/retest

@jmencak
Copy link
Contributor Author

jmencak commented Apr 30, 2025

/retest

1 similar comment
@jmencak
Copy link
Contributor Author

jmencak commented May 12, 2025

/retest

@MarSik
Copy link
Contributor

MarSik commented Jun 17, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 17, 2025
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD df3b43e and 2 for PR HEAD 7e15f86 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 17, 2025

@jmencak: all tests passed!

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.

@openshift-merge-bot openshift-merge-bot bot merged commit fd761db into openshift:main Jun 17, 2025
19 checks passed
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: cluster-node-tuning-operator
This PR has been included in build cluster-node-tuning-operator-container-v4.20.0-202506171813.p0.gfd761db.assembly.stream.el9.
All builds following this will include this PR.

@jmencak jmencak deleted the 4.20-tls13 branch June 17, 2025 19:54
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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants