AUTOSCALE-892: CMA: Add PQC ML-KEM CI test - #82248
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
WalkthroughThe OpenShift CI configuration adds a ChangesTLS scanner CI integration
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 Checkov (3.3.8)ci-operator/config/openshift/custom-metrics-autoscaler-operator/openshift-custom-metrics-autoscaler-operator-main.yamlTraceback (most recent call last): Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
/pj-rehearse pull-ci-openshift-custom-metrics-autoscaler-operator-main-cma-e2e-aws-ovn |
|
@shyadav10: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@shyadav10: This pull request references AUTOSCALE-892 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "5.0.0" version, but no target version was set. DetailsIn 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. |
|
It looks like I was wrong about being able to just add the TLS test at the end of any existing E2E. That E2E's workflow seems to completely remove CMA when it is finished. Let's take a look at how else we might be able to do this. I prefer the idea of adding it to an existing E2E so that we don't need an entire cluster install just for this one test, so let's think about how that could work |
What if we put the inline chain steps in the config, i.e replace - chain: keda-e2e-cma with the 6 individual step refs, and insert - ref: tls-scanner-run before - ref: keda-e2e-cma-teardown? Something like this? |
|
I think that is a great idea, but I think we would need to move the tls test up one notch since I think the clean step does some of the keda removal |
|
/pj-rehearse pull-ci-openshift-custom-metrics-autoscaler-operator-main-cma-e2e-aws-ovn |
|
@shyadav10: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/retest |
|
/pj-rehearse pull-ci-openshift-custom-metrics-autoscaler-operator-main-cma-e2e-aws-ovn |
|
@shyadav10: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
Ugh, that KEDA test is way too flaky! |
|
@joelsmith: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
Flaky test attempt number 3! |
|
@joelsmith: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Oops, not flaky after all. I think it's broken. The E2Es are trying to remove the keda ns and install, but we are installing via the CMA operator. I think I figured out why. I think we need to include the variables from https://github.com/openshift/release/blob/main/ci-operator/step-registry/keda/e2e/cma/keda-e2e-cma-chain.yaml#L11-L14 which are getting overwritten by our new Edit: I was right and wrong. We did need to add those, but my reasoning was wrong. We're not overwriting the chain, we're copying its important bits. Thanks for figuring it out despite my bad explanation. |
|
/pj-rehearse pull-ci-openshift-custom-metrics-autoscaler-operator-main-cma-e2e-aws-ovn |
|
@shyadav10: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse pull-ci-openshift-custom-metrics-autoscaler-operator-main-cma-e2e-aws-ovn |
|
@joelsmith: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
This looks great, but I would like to see it pass once before merging. The last run seemed to be a flake of the KEDA tests, so hopefully this next run will pass. Once the rehearsal job passes, feel free to merge it. Thanks! |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: joelsmith, shyadav10 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 |
|
/pj-rehearse pull-ci-openshift-custom-metrics-autoscaler-operator-main-cma-e2e-aws-ovn |
|
@joelsmith: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse ack |
|
@shyadav10: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
d5e33ea
into
openshift:main
* CMA: Add PQC ML-KEM CI test * restructured the test * changed env
* CMA: Add PQC ML-KEM CI test * restructured the test * changed env
Jira link: https://redhat.atlassian.net/browse/AUTOSCALE-892
Summary by CodeRabbit
Updates the OpenShift CI configuration for the Custom Metrics Autoscaler (CMA) AWS OVN end-to-end workflow to add post-quantum (ML-KEM) verification using a TLS scanning step. The change introduces a new
tls-scanner-toolbase image definition, setsPQC_CHECK,SCAN_NAMESPACE, and TLS scanner resource limits (SCANNER_CPU,SCANNER_MEMORY) for thecma-e2e-aws-ovnjob, and expands the E2E chain into explicit ordered refs sotls-scanner-runexecutes in the workflow before the existing cleanup/teardown steps.