Repository navigation
Use MLDSA65 algorithm in cert-manager Certificate manifests - #1122
openshift-merge-bot[bot] merged 1 commit into
Conversation
With this commit, cipher and key exchange algorithm is more PQC safe. Related-To: OSPRH-28427 Depends-On: openstack-k8s-operators#1117 Signed-off-by: Daniel Pawlik <dpawlik@redhat.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
|
Build succeeded (check pipeline). ✔️ s2i-openstack-container-content-provider SUCCESS in 12h 19m 48s Warning: |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danpawlik, vyzigold 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 |
|
just a not, I don't think the cert-manager we have currently available already supports MLDSA65. it just merged 2 weeks ago in cert-manager cert-manager/cert-manager#9469 . also Kubernetes API server needs Go 1.27 |
ac92ef5
into
openstack-k8s-operators:main
@stuggi How did we pass through tests though? Are the config/certmanager/* files actually used anywhere? Should we revert? |
those would only be used if you install telemetry-operator as standalone. the certs issued for deployment via the openstack-operator are like here openstack-k8s-operators/openstack-operator#1973 in the openstack-op and sync-bindata.sh If you check the cert from this PR CI run it uses |
|
@stuggi From the task: |
|
aha, it might fail in standalone deployment when certmanager overlay is used. Agree. Let's revert. |
|
/revert |
|
Revert done #1124 |
With this commit, cipher and key exchange algorithm is more PQC safe.
Related-To: OSPRH-28427
Depends-On: #1117
Depends-On: infrawatch/feature-verification-tests#476