Repository navigation
e2e: run the functional suite against a real OCP cluster - #559
Merged
openshift-merge-bot[bot] merged 1 commit intoOct 20, 2026
Merged
Conversation
openshift-ci
Bot
added
the
size/L
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gauron99 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
Bot
added
the
approved
Add hack/openshift/ to run the e2e suite against an existing OpenShift cluster an engineer is oc-login'd to: - prepare-ocp-cluster.sh: idempotent, env-gated setup. Installs Gitea (+ kube-public/gitea-endpoint ConfigMap), Red Hat OpenShift Pipelines, and (optionally) CMA for the keda deployer. No registry is deployed: the suite pushes to ttl.sh with on-cluster builds (FUNC_REMOTE=true). - run-e2e-tests.sh: sets REGISTRY to a fresh ttl.sh namespace, DEFAULT_DEPLOYER=raw, FUNC_REMOTE=true and FUNC_MANAGEMENT_DISABLED=true, and execs make test-e2e. - Makefile: pass E2E_SKIP and STALE_FUNCTION_IMAGE through to ginkgo. The default E2E_SKIP drops specs that cannot work under FUNC_REMOTE=true (details in run-e2e-tests.sh): the SSH-repository specs (need an exposed SSH endpoint), Middleware Update and registry-auth-secret (their stale-CLI seed premise breaks remotely), and the monorepo subdirectory spec (the remote seed deploy leaves the function name out of the committed func.yaml, so the operator's describe fails). The middleware-rebuild spec self-skips while STALE_FUNCTION_IMAGE is unset.
gauron99
force-pushed
the
push-txmuypkryoum
branch
from
October 19, 2026 14:20
9b93876 to
a4623a5
Compare
Author
|
/hold to merge after functions-dev#269 gets propagated downstream |
openshift-ci
Bot
added
the
do-not-merge/hold
Author
|
the E2E_SKIP in makefile is coming in via #579 |
|
/lgtm |
Author
|
/unhold |
openshift-ci
Bot
removed
the
do-not-merge/hold
|
@gauron99: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add hack/openshift/ to run the e2e suite against an existing OpenShift cluster an engineer is oc-login'd to:
prepare-ocp-cluster.sh: idempotent, env-gated setup. Installs Gitea (+ kube-public/gitea-endpoint ConfigMap), Red Hat OpenShift Pipelines, and (optionally) CMA for the keda deployer. No registry is deployed: the suite pushes to ttl.sh with on-cluster builds (FUNC_REMOTE=true).
run-e2e-tests.sh: sets REGISTRY to a fresh ttl.sh namespace, DEFAULT_DEPLOYER=raw, FUNC_REMOTE=true and FUNC_MANAGEMENT_DISABLED=true, and execs make test-e2e.
The default E2E_SKIP drops specs that cannot work under FUNC_REMOTE=true (currently -- details in run-e2e-tests.sh): the SSH-repository specs (need an exposed SSH endpoint), Middleware Update and registry-auth-secret (their stale-CLI seed premise breaks remotely), and the monorepo subdirectory spec (the remote seed deploy leaves the function name out of the committed func.yaml, so the operator's describe fails). The middleware-rebuild spec self-skips while STALE_FUNCTION_IMAGE is unset.