NO-JIRA: Add CI config for opendatahub-io/mcp-lifecycle-operator release-0.2

[matzew]

Add presubmit unit test job for the release-0.2 branch, mirroring the existing main branch configuration.

Summary by CodeRabbit

This pull request adds continuous integration configuration for the OpenDataHub MCP Lifecycle Operator's release-0.2 branch in the OpenShift CI infrastructure.

The change introduces a new CI operator configuration file that mirrors the existing setup for the main branch. The configuration defines:

• Build context and image definitions for the operator
• Default resource requests (CPU/memory) for Kubernetes resources
• Three presubmit pipeline jobs:
  • A lint job that runs make lint to check code style and formatting
  • A test job that runs make test to execute the test suite
  • An optional security job that performs security scanning (skipped when only certain files change)

This enables automated validation of code changes submitted to the release-0.2 branch before they are merged, covering code quality, correctness, and security aspects.

[openshift-ci-robot]

@matzew: This pull request explicitly references no jira issue.

Details

In response to this:

Add presubmit unit test job for the release-0.2 branch, mirroring the existing main branch configuration.

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.

[coderabbitai]

Walkthrough

Adds a new CI operator configuration YAML for opendatahub-io/mcp-lifecycle-operator targeting the release-0.2 branch. The file defines the build root, a Docker image mapping, default Kubernetes resource requests, and three test steps: lint, test, and an optional security pipeline with file-change-based skip rules.

Changes

release-0.2 CI Configuration

Layer / File(s)	Summary
release-0.2 CI pipeline definition ci-operator/config/opendatahub-io/mcp-lifecycle-operator/opendatahub-io-mcp-lifecycle-operator-release-0.2.yaml	Introduces the full ci-operator config: build root image, Dockerfile-to-output image mapping, global CPU/memory resource requests, lint step (make lint with Go cache env), test step (make test with Go module read-only flags), optional security step using openshift-ci-security with skip_if_only_changed rules, and zz_generated_metadata for branch/org/repo.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• openshift/release#80649: Adds the release-0.1 CI config for the same repository with an identical structure (image build, resource requests, lint/test/security pipelines), of which this PR is a direct release-0.2 counterpart.

Suggested labels

lgtm

Suggested reviewers

• cardil

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	The PR adds a CI operator YAML configuration file, not Ginkgo test code. The custom check for Ginkgo test name stability is not applicable to YAML CI configuration files.
Test Structure And Quality	✅ Passed	This PR adds CI operator configuration YAML files only, not Ginkgo test code. The check is not applicable to non-test code.
Microshift Test Compatibility	✅ Passed	PR only adds YAML CI configuration file, not Ginkgo e2e test code. MicroShift test compatibility check only applies when new Ginkgo tests (It(), Describe(), etc.) are added.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR adds only CI configuration YAML (no Ginkgo e2e tests). The check requires new test code with Ginkgo structures; this is infrastructure configuration mirroring existing main branch setup.
Topology-Aware Scheduling Compatibility	✅ Passed	PR adds only CI/CD infrastructure configuration files (ci-operator config and Prow presubmit jobs) with no deployment manifests, operator code, or scheduling constraints that would affect runtime t...
Ote Binary Stdout Contract	✅ Passed	PR adds only YAML CI configuration files for mcp-lifecycle-operator; check applies to Go test code stdout violations, not configuration files.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	This PR adds only a CI configuration YAML file, not Ginkgo e2e tests. The custom check for IPv6/disconnected network compatibility is not applicable.
No-Weak-Crypto	✅ Passed	PR adds only a YAML CI/CD configuration file with no weak cryptographic algorithms (MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB), custom crypto implementations, or secret comparisons.
Container-Privileges	✅ Passed	The new YAML configuration file does not contain any privileged container settings (privileged: true, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation, or runAsUser: 0).
No-Sensitive-Data-In-Logs	✅ Passed	The YAML config file contains no passwords, tokens, API keys, PII, session IDs, internal hostnames, or customer data; it only defines safe CI environment variables and standard build commands.
Title check	✅ Passed	The title accurately describes the main change: adding CI configuration for the mcp-lifecycle-operator release-0.2 branch, which is the primary purpose of the PR.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@matzew: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-opendatahub-io-mcp-lifecycle-operator-release-0.2-images	opendatahub-io/mcp-lifecycle-operator	presubmit	Presubmit changed
pull-ci-opendatahub-io-mcp-lifecycle-operator-release-0.2-lint	opendatahub-io/mcp-lifecycle-operator	presubmit	Presubmit changed
pull-ci-opendatahub-io-mcp-lifecycle-operator-release-0.2-security	opendatahub-io/mcp-lifecycle-operator	presubmit	Presubmit changed
pull-ci-opendatahub-io-mcp-lifecycle-operator-release-0.2-test	opendatahub-io/mcp-lifecycle-operator	presubmit	Presubmit changed

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[jaideepr97]

LGTM

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jaideepr97, matzew

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:

• ci-operator/config/opendatahub-io/mcp-lifecycle-operator/OWNERS [jaideepr97,matzew]
• ci-operator/jobs/opendatahub-io/mcp-lifecycle-operator/OWNERS [jaideepr97,matzew]

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

[openshift-ci]

@matzew: 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.