[WIP]OCPBUGS-37706: Modern TLS security profile support

[wangke19]

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[openshift-ci-robot]

@wangke19: 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:

• 833c0c2|Support modern TLS security Profile: 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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: wangke19
Once this PR has been reviewed and has the lgtm label, please assign jerpeter1 for approval. For more information see the Kubernetes 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

[openshift-ci-robot]

@wangke19: 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:

• eea8646|Support modern TLS security Profile: 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]

@wangke19: 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:

• e120bdc|Merge branch 'openshift:master' into modern-tlsprofile-support: does not specify an upstream backport in the commit message
• eea8646|Support modern TLS security Profile: 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]

@wangke19: 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:

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

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 refersh

[openshift-ci-robot]

@wangke19: 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:

• 3d5da06|Support modern TLS security Profile: 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]

@wangke19: 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:

• aea610c|Support modern TLS security Profile: 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]

@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/prow/e2e-gcp	aea610c	link	true	/test e2e-gcp
ci/prow/e2e-aws-ovn-runc	aea610c	link	true	/test e2e-aws-ovn-runc
ci/prow/artifacts	aea610c	link	true	/test artifacts
ci/prow/e2e-gcp-ovn-upgrade	aea610c	link	true	/test e2e-gcp-ovn-upgrade
ci/prow/integration	aea610c	link	true	/test integration
ci/prow/k8s-e2e-gcp-ovn	aea610c	link	true	/test k8s-e2e-gcp-ovn
ci/prow/images	aea610c	link	true	/test images
ci/prow/unit	aea610c	link	true	/test unit
ci/prow/e2e-aws-ovn-cgroupsv2	aea610c	link	true	/test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-agnostic-ovn-cmd	aea610c	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/k8s-e2e-aws-ovn-serial	aea610c	link	false	/test k8s-e2e-aws-ovn-serial
ci/prow/e2e-aws-crun-wasm	aea610c	link	true	/test e2e-aws-crun-wasm
ci/prow/e2e-aws-ovn-serial	aea610c	link	true	/test e2e-aws-ovn-serial
ci/prow/e2e-aws-ovn-fips	aea610c	link	true	/test e2e-aws-ovn-fips
ci/prow/e2e-aws-ovn-crun	aea610c	link	true	/test e2e-aws-ovn-crun
ci/prow/verify-commits	aea610c	link	true	/test verify-commits
ci/prow/k8s-e2e-conformance-aws	aea610c	link	true	/test k8s-e2e-conformance-aws
ci/prow/verify	aea610c	link	true	/test verify
ci/prow/k8s-e2e-gcp-serial	aea610c	link	true	/test k8s-e2e-gcp-serial
ci/prow/e2e-aws-csi	aea610c	link	false	/test e2e-aws-csi

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.

[wangke19]

Thist will be implemented in pr openshift/api#2069

[openshift-merge-robot]

PR needs rebase.

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.

[openshift-ci-robot]

@wangke19: This pull request references Jira Issue OCPBUGS-37706. The bug has been updated to no longer refer to the pull request using the external bug tracker.

In response to this:

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

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]

@wangke19: Closed this PR.

In response to this:

Thist will be implemented in pr openshift/api#2069
/close

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.