ci: update ib-kubernetes version to c89c59e (of branch network-operator-26.1.x)

[nvidia-ci-cd]

Automated CI update for component 'ib-kubernetes', created by GitHub actions reusable workflow run 28871934641 for release branch network-operator-26.1.x.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[greptile-apps]

Greptile Summary

Automated CI bump of the ib-kubernetes component version from network-operator-v26.7.0-beta.2 to commit SHA c89c59e, targeting the network-operator-26.1.x branch. All three version references are updated consistently.

• The version identifier changes from a descriptive semantic-version tag to a short Git commit SHA (c89c59e). While this is consistent across all three files, a raw SHA is less human-readable and harder to audit in changelogs or post-mortems compared to a named tag.
• All images are pinned to the nvcr.io/nvstaging/mellanox staging registry, so this update is for pre-release/staging use.

Confidence Score: 4/5

Safe to merge; all three version references are updated consistently and the target registry is staging.

The update is fully consistent across all three files and is automated by a CI bot. The only notable concern is that a bare commit SHA replaces a descriptive version tag, which reduces traceability in changelogs and makes rollbacks less intuitive — but this does not affect runtime correctness as long as the image exists at that tag in the staging registry.

hack/release.yaml is the source of truth for the release pipeline and is where the version identifier matters most for downstream tooling.

Important Files Changed

Filename	Overview
hack/release.yaml	Bumps ib-kubernetes version from network-operator-v26.7.0-beta.2 to raw commit SHA c89c59e — source of truth for the release pipeline
example/crs/mellanox.com_v1alpha1_nicclusterpolicy_cr-full.yaml	Updates ibKubernetes version field from network-operator-v26.7.0-beta.2 to commit SHA c89c59e consistently with the other changed files
example/crs/mellanox.com_v1alpha1_nicclusterpolicy_cr-full-ocp.yaml	Updates ibKubernetes version field from network-operator-v26.7.0-beta.2 to commit SHA c89c59e consistently with the other changed files (OCP variant)

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[CI Workflow Run\n28871934641] -->|Triggered by| B[ib-kubernetes branch\nnetwork-operator-26.1.x]
    B -->|Produces image at| C[nvcr.io/nvstaging/mellanox\n/ib-kubernetes:c89c59e]
    C -->|Version bumped in| D[hack/release.yaml]
    C -->|Version bumped in| E[example/crs/...cr-full.yaml]
    C -->|Version bumped in| F[example/crs/...cr-full-ocp.yaml]
    D & E & F -->|Previously| G[network-operator-v26.7.0-beta.2]
    D & E & F -->|Now| H[c89c59e]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[CI Workflow Run\n28871934641] -->|Triggered by| B[ib-kubernetes branch\nnetwork-operator-26.1.x]
    B -->|Produces image at| C[nvcr.io/nvstaging/mellanox\n/ib-kubernetes:c89c59e]
    C -->|Version bumped in| D[hack/release.yaml]
    C -->|Version bumped in| E[example/crs/...cr-full.yaml]
    C -->|Version bumped in| F[example/crs/...cr-full-ocp.yaml]
    D & E & F -->|Previously| G[network-operator-v26.7.0-beta.2]
    D & E & F -->|Now| H[c89c59e]

Loading

_{Reviews (1): Last reviewed commit: "ci: update ib-kubernetes version to c89c..." | Re-trigger Greptile}

[greptile-apps]

Raw commit SHA used as version identifier

The version is set to a bare short Git SHA (c89c59e) rather than a named tag (e.g., the previous network-operator-v26.7.0-beta.2). Short SHAs are ambiguous across repositories and can collide; they also make changelog auditing and rollback harder because there is no semantic context about what changed. If the CI pipeline produces a properly tagged image (or will tag one before this lands in a release), prefer using that tag here instead.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!