OCPNETUI-56: Add hot-cluster E2E workflows, composite actions, and Dockerfile.ci

[lkladnit]

Summary

GitHub Actions infrastructure for running Cypress E2E tests on a persistent (hot) OpenShift cluster via ARC self-hosted runners. Manual dispatch only (workflow_dispatch).

Workflows

File	Purpose
hot-cluster-e2e.yml	Entry point: manual dispatch, calls run workflow
hot-cluster-e2e-run.yml	Build plugin image → provision test env via Helm → run Cypress → collect diagnostics → tear down

Composite actions

Action	Purpose
ci-env-request	Create trigger ConfigMap, poll until environment ready, output bridge URL
ci-env-release	Patch ConfigMap to absent, wait for cleanup, delete ConfigMap

Docker

File	Purpose
Dockerfile.ci	Multi-stage build mirroring production Dockerfile, pinned UBI9 base images (GitHub Actions cannot pull from registry.ci.openshift.org)
.dockerignore	Exclude CI/test/git files from image context

FIPS cluster support

RHOS clusters with FIPS enabled cause segfaults in both the .NET-based GitHub Actions runner and the Go-based oc CLI. Workarounds applied:

• OPENSSL_FORCE_FIPS_MODE=0 for the runner process
• GOLANG_FIPS=0 for oc commands
• KUBECONFIG=/tmp/kubeconfig for non-root writable path

Changes addressing review feedback

• Dockerfile.ci: pinned base image versions, match production Dockerfile structure (CYPRESS_INSTALL_BINARY=0, --ignore-scripts)
• .dockerignore: relaxed scope — kept eslint/prettier configs, removed *.md exclusion
• Trigger: removed pull_request_target (security concern), kept workflow_dispatch only. PR-triggered runs can be added later via the safer pull_request + workflow_run pattern.
• Health check: removed separate job, replaced with inline oc cluster-info + node count after auth

Cluster setup prerequisites

See ci-scripts/README.md (from #489) for RHOS cluster preparation steps.

Depends on #489 (ci-scripts), #490 (ci-test-stack), #491 (ci-env-controller).

Jira: OCPNETUI-56

Test plan

• Workflow triggers via manual dispatch on a fork with ARC configured
• Plugin image builds and pushes to ttl.sh
• Helm provisions test environment on hot cluster
• Cypress tests execute against in-cluster console
• Cleanup tears down Helm release and namespaces

[openshift-ci]

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

GitHub Actions infrastructure for running Cypress E2E tests on a persistent (hot) OpenShift cluster via ARC self-hosted runners.

Workflows

File	Purpose
hot-cluster-e2e.yml	Entry point: PR gating (fork trust, ok-to-test label), health check, calls run workflow
hot-cluster-e2e-run.yml	Build plugin image → provision test env → run Cypress → collect diagnostics → tear down

Composite actions

Action	Purpose
ci-env-request	Create trigger ConfigMap, poll until ci-env-controller provisions environment, output bridge URL
ci-env-release	Patch ConfigMap to absent, wait for cleanup, delete ConfigMap

Docker

File	Purpose
Dockerfile.ci	Multi-stage build with public UBI9 base images (GitHub Actions cannot pull from registry.ci.openshift.org)
.dockerignore	Exclude CI/test files from image context

FIPS cluster support

RHOS clusters with FIPS enabled cause segfaults in both the .NET-based GitHub Actions runner and the Go-based oc CLI. Workarounds applied:

• OPENSSL_FORCE_FIPS_MODE=0 for the runner process
• GOLANG_FIPS=0 for oc commands
• KUBECONFIG=/tmp/kubeconfig for non-root writable path

Cluster setup prerequisites

See ci-scripts/README.md (from #489) for RHOS cluster preparation steps (ARC controller, runner scale set, ci-env-controller).

Depends on #489 (ci-scripts), #490 (ci-test-stack), #491 (ci-env-controller).

Jira: OCPNETUI-56

Test plan

• Workflow triggers via manual dispatch on a branch with ARC configured
• Health check passes on a RHOS cluster with ARC installed
• Plugin image builds and pushes to ttl.sh
• ci-env-controller provisions test environment
• Cypress tests run against in-cluster console

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: 8731833f-3f2f-4059-809e-e7f31c1b6c96

---

_{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.