Enabling the CI for GitOps 1.21.0

[Naveena-058]

Enable OpenShift CI for the redhat-developer/gitops-operator v1.21 branch, replacing the retired v1.18 configuration.

Summary by CodeRabbit

This PR establishes OpenShift CI configuration for the RedHat Developer gitops-operator v1.21 release branch. The changes add two new CI configuration files that enable continuous integration and testing for this branch:

Configuration Updates:

• redhat-developer-gitops-operator-v1.21.yaml: Minimal base configuration that specifies the v1.21 branch and defines unit testing steps
• redhat-developer-gitops-operator-v1.21__v4.21.yaml: Extended configuration for OpenShift 4.21 compatibility testing that includes:
  • Integration release targeting to OpenShift 4.21
  • Complete test suite with sequential KUTTL tests, parallel KUTTL tests, and full e2e tests
  • KUTTL test timeout set to 3h30m0s to accommodate the test duration

This replaces the previously retired v1.18 configuration and aligns the CI setup to test the gitops-operator v1.21 release branch against OpenShift 4.21, ensuring proper operator compatibility and functionality through automated CI/CD pipelines.

[openshift-ci]

Hi @Naveena-058. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 5dd94099-6f92-4929-bbc8-d78642ec39fe

📥 Commits

Reviewing files that changed from the base of the PR and between 2c4f316 and 43e7afd.

⛔ Files ignored due to path filters (1)

• ci-operator/jobs/redhat-developer/gitops-operator/redhat-developer-gitops-operator-v1.21-presubmits.yaml is excluded by !ci-operator/jobs/**

📒 Files selected for processing (2)

• ci-operator/config/redhat-developer/gitops-operator/redhat-developer-gitops-operator-v1.21.yaml
• ci-operator/config/redhat-developer/gitops-operator/redhat-developer-gitops-operator-v1.21__v4.21.yaml

---

Walkthrough

Two CI operator YAML configuration files for the GitOps Operator are updated to replace v1.18/v4.19 references with v1.21/v4.21. The releases.initial.integration name is changed to 4.21, the KUTTL test timeout is increased from 2h30m0s to 3h30m0s, and zz_generated_metadata is refreshed accordingly.

Changes

GitOps Operator CI Config Bump to v1.21/v4.21

Layer / File(s)	Summary
Branch, release, timeout, and metadata updates ci-operator/config/redhat-developer/gitops-operator/redhat-developer-gitops-operator-v1.21.yaml, ci-operator/config/redhat-developer/gitops-operator/redhat-developer-gitops-operator-v1.21__v4.21.yaml	Updates branch to v1.21, switches releases.initial.integration name from 4.19 to 4.21, increases KUTTL timeout from 2h30m0s to 3h30m0s, and refreshes zz_generated_metadata to branch: v1.21 and variant: v4.21.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Enabling the CI for GitOps 1.21.0' directly and clearly summarizes the main objective of the changeset: setting up continuous integration configuration for version 1.21.0 of the gitops-operator.
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 two CI configuration files with test and step names: unit, kuttl-sequential, kuttl-parallel, e2e (tests) and unit-steps, install, sequential-e2e-steps, parallel-e2e-steps, e2e-steps (st...
Test Structure And Quality	✅ Passed	This PR modifies only CI configuration YAML files for redhat-developer/gitops-operator. No Ginkgo test code is present; the custom check for Ginkgo test quality is not applicable.
Microshift Test Compatibility	✅ Passed	PR only modifies OpenShift CI YAML configuration files, not Ginkgo e2e test code. MicroShift Test Compatibility check is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This PR only updates CI configuration files (YAML) in the openshift/release repository. No new Ginkgo e2e tests are added. The check for SNO compatibility is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	This PR modifies only OpenShift CI operator configuration files (ci-operator/config), not deployment manifests, operator code, or controllers. These are CI infrastructure configuration changes, whi...
Ote Binary Stdout Contract	✅ Passed	The OTE Binary Stdout Contract check is not applicable: this PR modifies only CI configuration YAML files in the OpenShift release repository, not OTE binary source code or test implementations.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	This PR adds CI configuration YAML files for GitOps Operator v1.21, not new Ginkgo e2e tests. The check is only applicable when new Go test code with Ginkgo patterns (It(), Describe(), etc.) is add...
No-Weak-Crypto	✅ Passed	PR modifies only CI/CD YAML configuration files with no cryptographic code, weak crypto usage, custom implementations, or insecure comparisons detected.
Container-Privileges	✅ Passed	The PR modifies CI operator configuration files (not K8s manifests) for the gitops-operator v1.21 branch. No container privilege escalation flags (privileged, hostPID, hostNetwork, hostIPC, SYS_ADM...
No-Sensitive-Data-In-Logs	✅ Passed	No sensitive data (passwords, tokens, API keys, PII, session IDs, or customer data) are hardcoded or exposed in the modified YAML configuration files.

_{✏️ 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-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Naveena-058
Once this PR has been reviewed and has the lgtm label, please assign shakyav for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• ci-operator/config/redhat-developer/gitops-operator/OWNERS
• ci-operator/jobs/redhat-developer/gitops-operator/OWNERS

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

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@Naveena-058: 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-redhat-developer-gitops-operator-v1.21-unit	redhat-developer/gitops-operator	presubmit	Presubmit changed
pull-ci-redhat-developer-gitops-operator-v1.21-v4.21-ci-index-gitops-operator-bundle	redhat-developer/gitops-operator	presubmit	Presubmit changed
pull-ci-redhat-developer-gitops-operator-v1.21-v4.21-e2e	redhat-developer/gitops-operator	presubmit	Presubmit changed
pull-ci-redhat-developer-gitops-operator-v1.21-v4.21-images	redhat-developer/gitops-operator	presubmit	Presubmit changed
pull-ci-redhat-developer-gitops-operator-v1.21-v4.21-kuttl-parallel	redhat-developer/gitops-operator	presubmit	Presubmit changed
pull-ci-redhat-developer-gitops-operator-v1.21-v4.21-kuttl-sequential	redhat-developer/gitops-operator	presubmit	Presubmit changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

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.

[varshab1210]

/test all

[varshab1210]

/pj-rehearse

[openshift-merge-bot]

@varshab1210: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-merge-bot]

@varshab1210: needs-ok-to-test label found, no rehearsals will be run

[varshab1210]

/ok-to-test

[openshift-ci]

@Naveena-058: 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.