Skip to content

Add Konflux onboarding and reusable TLS scan pipeline - #83

Open
richardsonnick wants to merge 2 commits into
mainfrom
feat/konflux-tls-scan
Open

Add Konflux onboarding and reusable TLS scan pipeline#83
richardsonnick wants to merge 2 commits into
mainfrom
feat/konflux-tls-scan

Conversation

@richardsonnick

Copy link
Copy Markdown
Contributor

Summary

Adds konflux/ packaging so:

  1. tls-scanner can be onboarded to Konflux (Application / Component / ImageRepository drafts using Dockerfile.local).
  2. Layered products can reuse a git-resolved compliance-scan Pipeline from their own IntegrationTestScenario, parameterized by a target-cluster kubeconfig Secret.
  3. This repo can self-test Snapshot builds via smoke + TLS-fixture Job pipelines.

These CRs are not auto-applied from git — someone with tenant access must oc apply them. Only the Pipeline YAMLs are fetched at run time via resolverRef.

What's included

Path Role
konflux/application.yaml / component.yaml Onboard build (PaC generates .tekton/ separately)
konflux/pipelines/tls-scanner-compliance-scan.yaml Reusable Job-deploy scan for layered products
konflux/pipelines/tls-scanner-self-test.yaml Smoke + fixture + Job scan for this repo
konflux/pipelines/tls-scanner-smoke-test.yaml Light --version / --help check
konflux/integration-test-scenario.yaml Optional ITS drafts (revision currently feat/konflux-tls-scan)
konflux/README.md Apply order + consumer instructions

How to exercise this PR in Konflux

  1. Fill <TENANT_NAMESPACE> and apply application.yamlcomponent.yaml → merge Konflux's PaC onboarding PR when it appears.
  2. Apply integration-test-scenario.yaml (already points revision at this branch).
  3. Open/retest this PR — look for optional integration checks (tls-scanner-self-test, tls-scanner-smoke-test).
  4. Before merge: flip ITS revision values back to main and re-apply.

Until step 1–2 happen, GitHub will not show Konflux checks (there is no existing Application/Component for this repo).

Layered-product usage (after merge)

See konflux/README.md — consumers add one ITS pointing at:

konflux/pipelines/tls-scanner-compliance-scan.yaml

with TARGET_KUBECONFIG_SECRET set to their ephemeral env kubeconfig Secret. Pin revision to a tag/commit rather than tracking main unless intentional.

Test plan

  • YAML parses (python3 -c yaml.safe_load_all on all konflux/**/*.yaml)
  • Tenant admin applies Application + Component; PaC PR appears and merges
  • ITS applied with revision: feat/konflux-tls-scan
  • PR shows optional Konflux checks; smoke and/or self-test logs visible in Tekton UI
  • Confirm TEST_OUTPUT result is written
  • Flip ITS revision to main before merge
  • (Follow-up) First layered product wires compliance-scan with their kubeconfig Secret

Made with Cursor

Introduce konflux/ manifests so tls-scanner can be onboarded to a Konflux
tenant and layered products can consume a git-resolved compliance-scan
Pipeline from their own IntegrationTestScenario.

- Application/Component/ImageRepository drafts (Dockerfile.local for builds)
- Smoke + self-test pipelines for validating Snapshot builds in this repo
- Reusable compliance-scan pipeline parameterized by TARGET_KUBECONFIG_SECRET
- Docs for apply order and layered-product consumption
- ITS revision temporarily points at feat/konflux-tls-scan for PR validation

Co-authored-by: Cursor <cursoragent@cursor.com>
@openshift-ci
openshift-ci Bot requested review from rhmdnd and smith-xyz July 20, 2026 14:39
@openshift-ci

openshift-ci Bot commented Jul 20, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: richardsonnick

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 20, 2026
Fill Application/Component/ITS namespace fields so the manifests are ready to
apply against the ocp-isc Konflux workspace.

Co-authored-by: Cursor <cursoragent@cursor.com>
@openshift-ci

openshift-ci Bot commented Jul 20, 2026

Copy link
Copy Markdown

@richardsonnick: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant