From 4c88798de4e120013327c6bebff8e1669bf754a1 Mon Sep 17 00:00:00 2001 From: Gowtham Shanmugasundaram Date: Thu, 30 Jul 2026 21:21:06 +0530 Subject: [PATCH] Move tls-scanner-run to post phase with best_effort for opendatahub-operator The TLS scanner is a read-only audit step that should not block PRs on failure. Moving it from the test phase to post with best_effort ensures e2e results are not affected by scanner issues. Co-authored-by: Cursor --- .../opendatahub-io-opendatahub-operator-main.yaml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/ci-operator/config/opendatahub-io/opendatahub-operator/opendatahub-io-opendatahub-operator-main.yaml b/ci-operator/config/opendatahub-io/opendatahub-operator/opendatahub-io-opendatahub-operator-main.yaml index f37724eefcff3..786f52aacc215 100644 --- a/ci-operator/config/opendatahub-io/opendatahub-operator/opendatahub-io-opendatahub-operator-main.yaml +++ b/ci-operator/config/opendatahub-io/opendatahub-operator/opendatahub-io-opendatahub-operator-main.yaml @@ -158,7 +158,9 @@ tests: cpu: 2000m memory: 3Gi timeout: 3h0m0s + post: - ref: tls-scanner-run + best_effort: true workflow: generic-claim - as: opendatahub-operator-image-mirror postsubmit: true