HYPERFLEET-576 | Add hyperfleet-credential-provider binary to hyperfleet-e2e

[yingzhanredhat]

Summary by CodeRabbit

• Chores
  • Updated build configuration to include a credential provider in the deployment package.

[coderabbitai]

Walkthrough

This change introduces a new multi-stage build stage in the Dockerfile to fetch the hyperfleet-credential-provider binary from a container registry. The binary is then copied from this new stage into the final image at /usr/local/bin/. The diff adds five lines to implement the multi-stage fetch and copy operations.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• HYPERFLEET-488 | test: Update the dockerfile to meet Prow job usage #14: Modifies Dockerfile's multi-stage build and binary COPY steps, adjusting how binaries are copied into the final image.

Suggested reviewers

• AlexVulaj
• tzhou5

🚥 Pre-merge checks | ✅ 3

✅ 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 clearly and specifically describes the main change: adding the hyperfleet-credential-provider binary to the hyperfleet-e2e image, which aligns directly with the Dockerfile modifications shown in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

No actionable comments were generated in the recent review. 🎉

🧹 Recent nitpick comments

Dockerfile (1)

26-27: Consider pinning the image tag for reproducibility.

Using :latest can lead to non-reproducible builds since the underlying image may change between builds. Consider using a specific version tag or digest (e.g., @sha256:...) to ensure consistent builds.

That said, if the intent is to always pull the latest CI-built credential provider, this may be acceptable for your workflow.

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

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

[yasun1]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: yasun1

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 [yasun1]

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