OCPNETUI-56: Add CI scripts for hot-cluster E2E infrastructure

[lkladnit]

Summary

Add shell scripts and nginx configs for running E2E tests on a persistent (hot) OpenShift cluster via GitHub Actions + ARC:

Script	Purpose
check-cluster-health.sh	Pre-flight: API server, nodes, ARC runner set, storage, console route
test-cleanup.sh	Delete networking test resources (NADs, policies, routes, UDNs)
start-console.sh	Run off-cluster console container with bearer-token auth
start-plugin-container.sh	Run plugin image with nginx (HTTP or HTTPS)
resolve-console-image.sh	Match console image tag to cluster OCP version
_cluster-helpers.sh	CLI download URL resolution helpers
nginx-9080.conf / nginx-9443.conf	Nginx configs for plugin serving

These support both Docker-based local testing and the Helm-based ci-env-controller (charts in follow-up PR).

Adapted from kubevirt-plugin hot-cluster CI (CNV-74265, PR #4099).

Jira: OCPNETUI-56

Test plan

• bash ci-scripts/check-cluster-health.sh passes on a cluster with ARC installed
• Scripts are executable (chmod +x)

Made with Cursor

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@lkladnit: This pull request references OCPNETUI-56 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.1.0" version, but no target version was set.

Details

In response to this:

Summary

Add shell scripts and nginx configs for running E2E tests on a persistent (hot) OpenShift cluster via GitHub Actions + ARC:

Script	Purpose
check-cluster-health.sh	Pre-flight: API server, nodes, ARC runner set, storage, console route
test-cleanup.sh	Delete networking test resources (NADs, policies, routes, UDNs)
start-console.sh	Run off-cluster console container with bearer-token auth
start-plugin-container.sh	Run plugin image with nginx (HTTP or HTTPS)
resolve-console-image.sh	Match console image tag to cluster OCP version
_cluster-helpers.sh	CLI download URL resolution helpers
nginx-9080.conf / nginx-9443.conf	Nginx configs for plugin serving

These support both Docker-based local testing and the Helm-based ci-env-controller (charts in follow-up PR).

Adapted from kubevirt-plugin hot-cluster CI (CNV-74265, PR #4099).

Jira: OCPNETUI-56

Test plan

• bash ci-scripts/check-cluster-health.sh passes on a cluster with ARC installed
• Scripts are executable (chmod +x)

Made with Cursor

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]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 1408b164-957e-42a9-b9bf-93ab9afa7f57

---

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lkladnit

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:

• OWNERS [lkladnit]

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

[openshift-ci]

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