Skip to content

ci: update nic-configuration-operator version to 6354cff (of branch network-operator-26.1.x)#2189

Open
nvidia-ci-cd wants to merge 1 commit intomasterfrom
ci/update-nic-configuration-operator-version-to-6354cff
Open

ci: update nic-configuration-operator version to 6354cff (of branch network-operator-26.1.x)#2189
nvidia-ci-cd wants to merge 1 commit intomasterfrom
ci/update-nic-configuration-operator-version-to-6354cff

Conversation

@nvidia-ci-cd
Copy link
Collaborator

Automated CI update for component 'nic-configuration-operator', created by GitHub actions reusable workflow run 22054822543 for release branch network-operator-26.1.x.

Signed-off-by: nvidia-ci-cd <svc-cloud-orch-gh@nvidia.com>
@greptile-apps
Copy link

greptile-apps bot commented Feb 16, 2026

Greptile Summary

Automated CI update that bumps the nic-configuration-operator and nic-configuration-operator-daemon image tags from network-operator-v26.1.0-beta.7 to commit hash 6354cff (from the network-operator-26.1.x branch). The change is applied consistently across hack/release.yaml and both example CR files.

  • Updates nicConfigurationOperator and nicConfigurationConfigDaemon versions in hack/release.yaml to 6354cff
  • Updates matching image tags in both example NicClusterPolicy CRs (full and OCP variants)
  • STIG-FIPS variants (nicConfigurationOperatorStigFipsUbuntu, nicConfigurationOperatorStigFipsRhel, and their daemon counterparts) in hack/release.yaml remain at network-operator-v26.1.0-beta.7-stig-fips-{flavor} — this is expected for intermediate CI updates, as STIG-FIPS tags follow a different naming convention and are updated during the full release workflow

Confidence Score: 4/5

  • This PR is a low-risk automated version bump that is consistent across all changed files.
  • The change is a straightforward version update generated by CI automation. All three files are updated consistently. The only concern is that the version format shifts from a human-readable release tag to a raw commit hash, which slightly reduces traceability, but this is consistent with the PR's stated purpose of tracking a specific commit from the network-operator-26.1.x branch.
  • hack/release.yaml — verify that the STIG-FIPS variants not being updated is intentional for this CI pipeline.

Important Files Changed

Filename Overview
hack/release.yaml Updates nicConfigurationOperator and nicConfigurationConfigDaemon versions from network-operator-v26.1.0-beta.7 to commit hash 6354cff. STIG-FIPS variants (Ubuntu/RHEL) for both operator and daemon are not updated and remain at the old beta.7 tags.
example/crs/mellanox.com_v1alpha1_nicclusterpolicy_cr-full-ocp.yaml Updates example OCP CR to use 6354cff for both nic-configuration-operator and daemon images, consistent with hack/release.yaml.
example/crs/mellanox.com_v1alpha1_nicclusterpolicy_cr-full.yaml Updates example CR to use 6354cff for both nic-configuration-operator and daemon images, consistent with hack/release.yaml.

Flowchart

flowchart TD
    A["CI Workflow\n(nic-configuration-operator repo)"] -->|"Triggers automated PR"| B["hack/release.yaml"]
    B -->|"nicConfigurationOperator\nversion: 6354cff"| C["Base Operator Image"]
    B -->|"nicConfigurationConfigDaemon\nversion: 6354cff"| D["Base Daemon Image"]
    B -->|"StigFips variants\nversion: unchanged"| E["STIG-FIPS Images\n(updated during full release)"]
    B --> F["Example CRs"]
    F -->|"operator version: 6354cff"| G["cr-full.yaml"]
    F -->|"operator version: 6354cff"| H["cr-full-ocp.yaml"]
Loading

Last reviewed commit: a247032

Copy link

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

3 files reviewed, no comments

Edit Code Review Agent Settings | Greptile

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.

1 participant