Skip to content

fix: use oc CLI instead of kubectl in E2E container#294

Open
yossiovadia wants to merge 2 commits into
opendatahub-io:mainfrom
yossiovadia:fix/oc-cli-e2e
Open

fix: use oc CLI instead of kubectl in E2E container#294
yossiovadia wants to merge 2 commits into
opendatahub-io:mainfrom
yossiovadia:fix/oc-cli-e2e

Conversation

@yossiovadia
Copy link
Copy Markdown
Contributor

Summary

  • Replace kubectl with oc in the E2E Dockerfile and entrypoint script for OpenShift/Konflux compatibility
  • Download oc from Red Hat mirror (stable-4.17 channel) — the tarball includes both oc and kubectl
  • Go test helpers use KUBECTL_BIN env var (default: oc) so local runs can override with kubectl
  • setup-kind.sh is unchanged — it targets Kind clusters where kubectl is correct

Per DevTestOps team request to use oc in E2E test containers.

Test plan

  • go vet ./test/e2e/ — clean
  • make lint — 0 issues
  • Verify Dockerfile builds with oc download (CI)
  • E2E on Konflux with oc (CI)

Replace kubectl with oc in the E2E Dockerfile and entrypoint script
for OpenShift compatibility. The oc tarball also includes kubectl, so
both are available. Go test helpers use KUBECTL_BIN env var (default: oc)
for local override.

setup-kind.sh is unchanged — it targets Kind clusters where kubectl
is the correct tool.
@openshift-ci openshift-ci Bot requested a review from nirrozenbaum May 19, 2026 16:01
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 19, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: yossiovadia

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:

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

@openshift-ci openshift-ci Bot requested a review from szedan-rh May 19, 2026 16:01
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 19, 2026

Warning

Rate limit exceeded

@yossiovadia has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 5 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: bfac52e8-a091-4abc-bfed-6b65dc7bb321

📥 Commits

Reviewing files that changed from the base of the PR and between 7eafecb and 07f0208.

📒 Files selected for processing (3)
  • Dockerfile.e2e
  • test/e2e/e2e_suite_test.go
  • test/e2e/scripts/entrypoint.sh

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 19, 2026
@github-actions github-actions Bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label May 19, 2026
The GitHub Actions runner has kubectl but not oc. Default to kubectl
in Go tests; the E2E container entrypoint uses oc directly.
@rhods-ci-bot
Copy link
Copy Markdown

@yossiovadia: The following test has Succeeded:

OCI Artifact Browser URL

View in Artifact Browser

Inspecting Test Artifacts Manually

To inspect your test artifacts manually, follow these steps:

  1. Install ORAS (see the ORAS installation guide).
  2. Download artifacts with the following commands:
mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/opendatahub/odh-ci-artifacts:ai-gateway-group-test-nnxhx

@yossiovadia yossiovadia requested a review from chaitanya1731 May 21, 2026 17:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants