Skip to content

Conversation

@katexochen
Copy link
Member

@katexochen katexochen commented Jan 7, 2026

Previously, Contrast allowed GPU model-specific resource types (such as nvidia.com/GH100_H100L_94GB) instead of the generic nvidia.com/pgpu to support heterogeneous hardware configurations. However, as Kata upstream isn't supporting this, this is switched to setup the Nvidia operator with the pGPU alias instead. We might be able to revert to the resource specific annotations in the future, depending on the upstream support for it.

As a user, follow the updated setup instructions for the Nvidia GPU operator and use nvidia.com/pgpu in resource limit.

@katexochen katexochen requested a review from burgerdev as a code owner January 7, 2026 13:19
@katexochen katexochen added the breaking change A user-affecting breaking change label Jan 7, 2026
@github-actions
Copy link

github-actions bot commented Jan 7, 2026

Do the documentation changes need to be backported?

Changes to /docs/docs won't be visible until the next release.
If you are fixing something in the docs that should be immediately visible, the changes needs to be made to both /docs/docs and /docs/versioned_docs/version-X.Y, where X.Y is the version of the latest minor release.
This can be done in this same PR.

  • Yes, this should be backported to the current version of the docs.
  • No, the PR only contains docs changes relevant for future versions.

@github-actions
Copy link

github-actions bot commented Jan 7, 2026

PR Preview Action v1.6.3
Preview removed because the pull request was closed.
2026-01-09 11:09 UTC

@katexochen katexochen merged commit d53b70d into main Jan 9, 2026
16 checks passed
@katexochen katexochen deleted the p/gpu-alias branch January 9, 2026 11:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breaking change A user-affecting breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants