[Pratik-Redhat-Tech]

What does this PR do?

Removes unused hack/non-olm-install (installer script, README, and RBAC patch). That installer is unused and was confusing contributors; #1287 asks to delete it rather than fix it.

Fixes #1287

NON_OLM=true e2e skips for a plain Deployment install are unchanged. Those live under test/openshift/e2e/ and are not this installer.

PR acceptance criteria:

• Documentation was updated and verified using make serve-docs OR not applicable (the only docs for this path lived in hack/non-olm-install/README.md, which is removed with the unused installer)
• Unit tests were updated OR not applicable (no product / Go code change)
• E2E tests were updated OR not applicable (e2e NON_OLM skips are a separate test fixture)

What type of PR is this?

/kind cleanup

How I validated

From the branch root:

test ! -d hack/non-olm-install && echo PASS: installer dir gone

rg -n 'hack/non-olm-install' || echo PASS: no remaining path refs

rg -n 'func EnvNonOLM' test/openshift/e2e/ginkgo/fixture/fixture.go

Results:

• hack/non-olm-install is gone (README, install-gitops-operator.sh, rbac-patch.yaml)
• no remaining hack/non-olm-install references
• EnvNonOLM() is still in the e2e fixture

No go test / e2e change: this is a directory delete only.

How to reproduce (reviewer)

git fetch origin pull/1442/head:pr-1442
git checkout pr-1442
test ! -d hack/non-olm-install
rg -n 'hack/non-olm-install' || true
ls hack/non-olm-install 2>&1 | cat

On master the directory exists; on this branch it does not. Product install path is still OLM (make bundle / OperatorHub), unchanged.

Special notes to the reviewer:

Watch that only hack/non-olm-install/ is removed. Do not drop NON_OLM e2e skips.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign chetan-rns 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:

• OWNERS

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

[openshift-ci]

Hi @Pratik-Redhat-Tech. Thanks for your PR.

I'm waiting for a redhat-developer 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), Organization UI (inherited)
• Review profile: CHILL
• Plan: Advanced
• Run ID: 478176a1-e218-4bbd-83b6-1626e44e782d

📥 Commits

Reviewing files that changed from the base of the PR and between efe358c and 0225efb.

📒 Files selected for processing: 3

• hack/non-olm-install/README.md
• hack/non-olm-install/install-gitops-operator.sh
• hack/non-olm-install/rbac-patch.yaml

🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

• argoproj-labs/argocd-operator (manual)

💤 Files with no reviewable changes: 3

• hack/non-olm-install/rbac-patch.yaml
• hack/non-olm-install/install-gitops-operator.sh
• hack/non-olm-install/README.md

Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review.

📝 Summary

Summary by CodeRabbit

• Chores
  • Removed the non-OLM installation utility and its accompanying documentation.
  • Removed the associated RBAC patch configuration used by the utility.

The non-OLM installer script was deleted, along with its README and RBAC patch. These files covered installation, uninstallation, and OLM migration workflows.

Changes: Non-OLM installer removal

Layer / File(s)	Summary
Remove installer and supporting assets hack/non-olm-install/install-gitops-operator.sh, hack/non-olm-install/rbac-patch.yaml, hack/non-olm-install/README.md	The installer script, its usage documentation, and its RBAC patch were deleted.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other · Severity of issue fixed: Low

Merge Risk: ⚪ Minimal · up to 0225e

This removes an unused installer script, its README, and its RBAC patch. Nothing in the repository depends on them, and the NON_OLM E2E behavior is unchanged, so it is safe to merge.

Pre-merge checks: 5

Check name	Status	Explanation
Title check		The title clearly and concisely describes removal of the unused non-OLM installer directory.
Linked Issues check		Issue #1287 requests deletion of the unused hack/non-olm-install directory. The merge-base-to-head diff deletes its README.md, install-gitops-operator.sh, and rbac-patch.yaml. This implements …
Out of Scope Changes check		The reviewed changes are limited to deleting the three files in hack/non-olm-install. The deletion directly supports issue #1287. No unrelated product, test, or documentation changes are shown.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Description check		The description clearly explains the removal of the unused hack/non-olm-install directory and identifies the retained NON_OLM E2E skips.

Full details: Linked Issues check

Explanation

Issue #1287 requests deletion of the unused hack/non-olm-install directory. The merge-base-to-head diff deletes its README.md, install-gitops-operator.sh, and rbac-patch.yaml. This implements the issue objective.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files.

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

[olivergondza]

/ok-to-test

To be sure these are not referenced somewhere in the depth of CI...