chore: use universal developer image in devfile

[tolusha]

What does this PR do?

Switches the repository devfile to the community
quay.io/devfile/universal-developer-image:ubi9-latest tooling image
instead of the project-maintained quay.io/eclipse/che-operator-dev:latest.

Screenshot/screencast of this PR

N/A — developer environment / CI change only, no user-facing behaviour.

What issues does this PR fix or reference?

N/A

How to test this PR?

N/A

Common Test Scenarios

• Deploy Eclipse Che
• Start an empty workspace
• Open terminal and build/run an image
• Stop a workspace
• Check operator logs for reconciliation errors or infinite reconciliation loops

PR Checklist

As the author of this Pull Request I made sure that:

• The Eclipse Contributor Agreement is valid
• Code produced is complete
• Code builds without errors
• Tests are covering the bugfix — N/A, no code change
• The repository devfile is up to date and works
• Relevant user documentation updated — N/A
• Relevant contributing documentation updated
• CI/CD changes implemented, documented and communicated

Reviewers

Reviewers, please comment how you tested the PR when approving it.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Development Environment
  • The development environment now uses the UBI 9 universal developer image instead of the project-specific image.
  • The automated build and publishing process for the previous image has been removed. As a result, development environments rely on the universal image rather than a separately built project image.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: tolusha

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

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: fa67a075-dcbc-4b40-915b-97bc7b8f0c5c

📥 Commits

Reviewing files that changed from the base of the PR and between f71d510 and cad80f0.

📒 Files selected for processing (3)

• .devfile.Dockerfile
• .github/workflows/devfile-ci.yaml
• devfile.yaml

💤 Files with no reviewable changes (2)

• .github/workflows/devfile-ci.yaml
• .devfile.Dockerfile

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The devfile tooling container now uses quay.io/devfile/universal-developer-image:ubi9-latest. The custom developer image Dockerfile and the workflow that built and pushed that image were removed.

Changes

Devfile tooling image

Layer / File(s)	Summary
Switch the tooling image .devfile.Dockerfile, .github/workflows/devfile-ci.yaml, devfile.yaml	tooling-container now uses the universal developer image. The Dockerfile that installed Go, chectl, and goimports, and the workflow that built and pushed the custom image, were removed.

Priority: ⬇️ Low

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

Change: Other

Merge Risk: ⚪ Minimal · up to cad80

No demonstrated workspace failure blocks merging. Confirm the Go version and run the proposed build and test checks as part of normal validation.

Architecture Summary

Architecture risk: 🔵 Low · up to cad80

The change affects 1 system.

Changed systems: devfile.yaml

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — devfile.yaml (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in devfile.yaml: tooling-container now uses quay.io/devfile/universal-developer-image:ubi9-latest instead of quay.io/eclipse/che-operator-dev:latest.
• observed — Modified behavior in .devfile.Dockerfile: The Dockerfile was removed, including its base image declaration and setup of Go 1.26.5, chectl, and goimports.
• observed — Modified behavior in .github/workflows/devfile-ci.yaml: The workflow that built and pushed the devfile container on matching main pushes was removed, including its checkout, build setup, registry login, and image-push steps.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	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…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: replacing the custom tooling image with the universal developer image in the devfile.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

New operator image available: quay.io/eclipse/che-operator:pr-2206-arm64

[github-actions]

New operator image available: quay.io/eclipse/che-operator:pr-2206-amd64

[tolusha]

Hi! I'm che-ai-assistant — I help with your pull requests.

I check for new comments every 10m0s, so there may be a short delay before I respond.

Available commands:

• /che-ai-assistant generate-che-doc — Generate a documentation PR based on this PR's changes
• /che-ai-assistant ok-pr-review — Run a comprehensive PR review (summary, code review, deep review, impact analysis)
• /che-ai-assistant ok-pr-readiness — Ensure PR has validation steps
• /che-ai-assistant check-pr-test-failures — Analyze failing CI checks, identify root causes, and suggest fixes
• /che-ai-assistant update-che-e2e-tests — Update Eclipse Che e2e tests
• /che-ai-assistant claude — Run a free-form instruction on this PR
• /che-ai-assistant help — Show this help message

[openshift-ci]

@tolusha: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/v19-upgrade-stable-to-next	cad80f0	link	true	/test v19-upgrade-stable-to-next
ci/prow/v19-devworkspace-happy-path	cad80f0	link	true	/test v19-devworkspace-happy-path

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.