fix: build of bundle failing in CI/merge

[mangelajo]

Summary by CodeRabbit

• Chores
  • Updated CI/CD build configuration for bundle image generation.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The CI workflow build configuration was updated to reference the bundle image Dockerfile at a new path. The configuration now points to deploy/operator/bundle.Dockerfile instead of the root-level bundle.Dockerfile, maintaining the same build logic.

Changes

Cohort / File(s)	Summary
CI workflow build configuration .github/workflows/build.yaml	Updated bundle image build to reference deploy/operator/bundle.Dockerfile instead of bundle.Dockerfile

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

• Verify that the Dockerfile exists at the new path deploy/operator/bundle.Dockerfile
• Confirm the file contents are identical or appropriate for the relocation
• Ensure no other workflow steps depend on the old root-level Dockerfile path

Poem

🐰 A Dockerfile found its new home,
In deploy/operator it now roams,
The path was adjusted with care,
The workflow's updated and fair,
No logic disturbed, just a tidy refold! 📁

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'fix: build of bundle failing in CI/merge' directly describes the main change: fixing a bundle build issue in the CI workflow. The change modifies the Dockerfile path in the build configuration, which is the precise fix for the CI build failure.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bundle-ci-fix

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ba1e02b and 5c00c89.

📒 Files selected for processing (1)

• .github/workflows/build.yaml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)

• GitHub Check: e2e-tests-release-0-7
• GitHub Check: e2e-tests (ubuntu-24.04)
• GitHub Check: e2e-tests (ubuntu-24.04-arm)
• GitHub Check: lint-go
• GitHub Check: tests
• GitHub Check: e2e-test-operator
• GitHub Check: deploy-kind

🔇 Additional comments (1)

.github/workflows/build.yaml (1)

29-31: Verify the Dockerfile exists at the new path.

The change relocates the bundle image Dockerfile to deploy/operator/bundle.Dockerfile with matching build context. This aligns well with organizing operator-related build artifacts in a dedicated directory. However, confirm that the file exists at this new location to ensure the CI build will succeed.

Warning

Tools execution failed with the following error:

Failed to run tools: 13 INTERNAL: Received RST_STREAM with code 2 (Internal server error)

---

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 and usage tips.}