Skip to content

ci: update sriov-network-operator version to c409fc2c1 (of branch network-operator-26.10.x) - #3399

Closed
nvidia-ci-cd wants to merge 1 commit into
masterfrom
ci/update-sriov-network-operator-version-to-c409fc2c1
Closed

nvidia-ci-cd wants to merge 1 commit into
masterfrom
ci/update-sriov-network-operator-version-to-c409fc2c1

Conversation

@nvidia-ci-cd

Copy link
Copy Markdown
Collaborator

Automated CI update for component 'sriov-network-operator', created by GitHub actions reusable workflow run 37432878062 for release branch network-operator-26.10.x.

Component updates

SriovNetworkOperator

  • Previous version in hack/release.yaml: network-operator-v26.10.0-beta.2
  • New version: c409fc2c1

Commits from network-operator-v26.10.0-beta.2 to c409fc2c1:

SriovNetworkOperatorWebhook

  • Previous version in hack/release.yaml: network-operator-v26.10.0-beta.2
  • New version: c409fc2c1

Commits from network-operator-v26.10.0-beta.2 to c409fc2c1:

SriovConfigDaemon

  • Previous version in hack/release.yaml: network-operator-v26.10.0-beta.2
  • New version: c409fc2c1

Commits from network-operator-v26.10.0-beta.2 to c409fc2c1:

Signed-off-by: nvidia-ci-cd <svc-cloud-orch-gh@nvidia.com>
@copy-pr-bot

copy-pr-bot Bot commented Oct 6, 2026

Copy link
Copy Markdown

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-apps Bot commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerConfidence Score: 4/5

[High risk] Updates container image versions for network operator deployment.

The PR appears safe to merge, though the new image tags should be validated before deployment.

Findings

  1. P2 New image tags go unchecked ▶

Summary

The PR updates the SR-IOV operator, config-daemon, and webhook image references and release defaults from the beta release tag to c409fc2c1.

  • The release workflow’s image-availability check does not cover the newly referenced tags.

Reviews (1) · Last reviewed commit: "ci: update sriov-network-operator versio..."

Comment on lines +163 to +164
operator: nvcr.io/nvstaging/mellanox/sriov-network-operator:c409fc2c1
sriovConfigDaemon: nvcr.io/nvstaging/mellanox/sriov-network-operator-config-daemon:c409fc2c1

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 New image tags go unchecked The operator, config-daemon, and webhook now use :c409fc2c1, but the release workflow checks availability only for its release-derived tag. If any of the new tags is missing from the registry, that check will pass and the chart will fail to pull the image at deployment. Please validate the tags referenced by these values.

@rollandf rollandf closed this Oct 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants