introduce Curves configuration to Ingress#6300
introduce Curves configuration to Ingress#6300eslutsky wants to merge 5 commits intoopenshift:mainfrom
Conversation
Signed-off-by: Evgeny Slutsky <eslutsky@redhat.com>
Signed-off-by: Evgeny Slutsky <eslutsky@redhat.com>
Signed-off-by: Evgeny Slutsky <eslutsky@redhat.com>
Signed-off-by: Evgeny Slutsky <eslutsky@redhat.com>
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
Skipping CI for Draft Pull Request. |
Signed-off-by: Evgeny Slutsky <eslutsky@redhat.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: eslutsky The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
The OWNERS file contains untrusted users, which makes it INVALID. The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the openshift org. You can then trigger verification by writing
|
To support new PQC key exchanges add option to set configure ingress ssl curves.
API specs change NE-2334: Implement enhancement in OpenShift API to support for TLS curves in TLSProfile api#2583
curves ingress support Add support for configurable SSL curves in HAProxy configuration router#678
example providing custom curves in MicroShift config:
in case curves configuration is not provided, then
ROUTER_CURVESwont be passed to the ingress deployment, and OpenSSL defaults curves will be used ( as it is in previous versions).