Release v25.1.0-beta.1

[e0ne]

Release Checklist

• Network-operator related component versions in Helm chart are up to date. (otherwise, submit PR to update)
  • node-feature-discovery
  • SR-IOV Network Operator
    • Verify that new versions of operator, configdaemon and webhooks components are compatible
    • Use latest releases of sriovcni and ibsriovcni
  • Manifest related component default versions
• Example folder is up to date (otherwise submit PR to update)
• Update network-operator Helm Chart.yaml with the release version (appVersion, version fields)

       > ./scripts/releases/prepare-release.sh v0.1.2 "Jane Doe <[email protected]>"
  

  • Ensure Helm CI is passing on updated Chart.
• Create a new github release
  • Release title: vx.y.z, Release description: Changelog from this issue
  • Release artifacts for current release
• Update gh-pages branch using the script

       > ./scripts/releases/update-gh-pages.sh -p <remote_fork> network-operator-0.1.2.tgz
  

  Or do it manually:
  • Create Helm package (master branch on release tag commit):

      > helm package deployment/network-operator
    

  • Place Helm package under gh-pages branch in release dir
  • Update index.yaml file under gh-pages branch in release dir:

      > # assuming we are under release dir
      > mkdir tmpdir; cp <helm-package.tgz> ./tmpdir
      > helm repo index ./tmpdir --url https://mellanox.github.io/network-operator/release --merge ./index.yaml
      > mv -f ./tmpdir/index.yaml ./; rm -rf ./tmpdir
    

  • Push to remote:

      > git add <helm .tgz package> <release/index.yaml> <README.md>
      > git commit -s -m "Release Network-Operator vx.y.z"
      > git push ...
    

  After that:
  • Update gh-pages branch README.md with deployment/README.md from master branch (on release tag commit)
  • Submit PR against gh-pages branch
• Add a link to the release in this issue
• Verify new image is published to the registry
• Close this issue

Changelog

New Features

Bug Fixes

Known Limitations

[nvidia-ci-cd]

Release automation started...

[wcrum]

Would like to reference #1212 to confirm if node-feature-discovery should be on 0.15.6 or bumping it to the same as NVIDIA GPU Operator (0.17.0). Additionally comparing to deployments of GPU Operator there is distribution issues without Chart.lock file within the deploment/network-operator directory.

Additionally would like to see if there should be parity between folder structure, deployment and deployments.

Happy to open PR if there is clarification.

https://github.com/NVIDIA/gpu-operator/blob/f7dc6d7901a66acf8643ee01a03fb74726531009/deployments/gpu-operator/Chart.yaml#L20-L24

https://github.com/NVIDIA/gpu-operator/blob/main/deployments/gpu-operator/Chart.lock