chore(deps): bump github.com/kubeflow/mpi-operator from 0.6.0 to 0.8.0

[dependabot]

Bumps github.com/kubeflow/mpi-operator from 0.6.0 to 0.8.0.

Release notes

Sourced from github.com/kubeflow/mpi-operator's releases.

v0.8.0

Changes since v0.7.0

• Features:
  • Support Mutable Scheduling Directives for suspended Jobs on Launcher Job, which allows us to propagate the scheduling directives from the MPIJob Launcher template to the Launcher batch/v1 Job only when in the suspended state. (#772, @​GonzaloSaez)
• Clean ups:
  • Upgrade Kubernetes dependencies to v1.35. (#769, @​tenzen-y)

Acknowledgments

Thank you to all the contributors (in no particular order): @​mimowo @​terrytangyuan @​GonzaloSaez @​tenzen-y

v0.7.0

Changes since v0.6.0

• Features:
  • Support custom cluster domain in MPI hostfile generation. (#704, #707, #738, @​tenzen-y)
  • Enable Service publishNotReadyAddresses when runLauncherAsWorker to improve DNS discovery for workers. (#703, @​tenzen-y)
  • Expose job controller workqueue rate-limiting configuration via operator flags to improve scalability tuning. (#674, @​rotemelad)
• Bug fixes:
  • Fix crash in PodGroup when runLauncherAsWorker=true. (#669, @​GonzaloSaez)
  • Fix missing ReplicaIndexLabel when runLauncherAsWorker=true so the launcher pod gets the expected pod index label (helps Kueue/TAS rank discovery). (#690, @​GonzaloSaez)
• Clean ups:
  • Upgrade Kubernetes dependencies to v1.34. (#742, @​tenzen-y)
  • Fix kustomize v5 warnings in manifests. (#700, @​vikas-saxena02)
  • Upgrade Debian version to trixie and MPI versions are upgraded in the following: (#685, @​tenzen-y)
    • OpenMPI: v4.1.4 -> v5.0.7
    • MPICH: v3.4.1 -> v4.2.1

Acknowledgments

Thank you to all the contributors (in no particular order): @​rotemelad @​mimowo @​terrytangyuan @​GonzaloSaez @​vikas-saxena02 @​tenzen-y

Changelog

Sourced from github.com/kubeflow/mpi-operator's changelog.

Release v0.8.0

• Features:
  • Support Mutable Scheduling Directives for suspended Jobs on Launcher Job, which allows us to propagate the scheduling directives from the MPIJob Launcher template to the Launcher batch/v1 Job only when in the suspended state. (#772, @​GonzaloSaez)
• Clean ups:
  • Upgrade Kubernetes dependencies to v1.35. (#769, @​tenzen-y)

Release v0.7.0

• Features:
  • Support custom cluster domain in MPI hostfile generation. (#704, #707, #738, @​tenzen-y)
  • Enable Service publishNotReadyAddresses when runLauncherAsWorker to improve DNS discovery for workers. (#703, @​tenzen-y)
  • Expose job controller workqueue rate-limiting configuration via operator flags to improve scalability tuning. (#674, @​rotemelad)
• Bug fixes:
  • Fix crash in PodGroup when runLauncherAsWorker=true. (#669, @​GonzaloSaez)
  • Fix missing ReplicaIndexLabel when runLauncherAsWorker=true so the launcher pod gets the expected pod index label (helps Kueue/TAS rank discovery). (#690, @​GonzaloSaez)
• Clean ups:
  • Upgrade Kubernetes dependencies to v1.34. (#742, @​tenzen-y)
  • Fix kustomize v5 warnings in manifests. (#700, @​vikas-saxena02)
  • Upgrade Debian version to trixie and MPI versions are upgraded in the following: (#685, @​tenzen-y)
    • OpenMPI: v4.1.4 -> v5.0.7
    • MPICH: v3.4.1 -> v4.2.1

Commits

• 101db14 Update the mpi-operator image with 0.8.0
• b8f8454 Update image tag with release-0.8 (#777)
• 83100a9 Prepare release v0.7.1 (#776)
• c72caac Fix launcher job scheduling directives when unsuspending (#772)
• 9504d8c Bump github.com/golangci/golangci-lint/v2 from 2.8.0 to 2.9.0 (#773)
• 4954c99 Bump k8s dependencies to v1.35.1 (#769)
• de2b0fe Bump github.com/onsi/gomega from 1.38.3 to 1.39.1 (#767)
• d0f7861 Bump golang.org/x/crypto from 0.46.0 to 0.47.0 (#764)
• b79ca70 Bump github.com/golangci/golangci-lint/v2 from 2.7.2 to 2.8.0 (#762)
• 35b1421 Remove empty rules (#766)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[enoodle]

@dependabot rebase

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 30f1d744-1a0a-4982-a9c4-825f06575402

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dependabot/go_modules/v0.4/github.com/kubeflow/mpi-operator-0.8.0

---

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

[enoodle]

@dependabot rebase

[davidLif]

closing dependabot PRs taht are not related to security updates

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.