Skip to content

Restore static MIG configs#2121

Open
rajathagasthya wants to merge 1 commit intomainfrom
dynamic-mig-config
Open

Restore static MIG configs#2121
rajathagasthya wants to merge 1 commit intomainfrom
dynamic-mig-config

Conversation

@rajathagasthya
Copy link
Contributor

@rajathagasthya rajathagasthya commented Feb 11, 2026

This change restores static MIG configs due to issues with R535 drivers not being able to detect MIG profiles. The configmap is volume mounted onto the MIG manager container as config-default.yaml, so that MIG manager can fall back to this config whenever generation fails.

Description

Checklist

  • No secrets, sensitive information, or unrelated changes
  • Lint checks passing (make lint)
  • Generated assets in-sync (make validate-generated-assets)
  • Go mod artifacts in-sync (make validate-modules)
  • Test cases are added for new code paths

Testing

Tested as part of NVIDIA/mig-parted#312

@coveralls
Copy link

coveralls commented Feb 12, 2026

Coverage Status

coverage: 26.159% (+0.04%) from 26.122%
when pulling db0bb63 on dynamic-mig-config
into f2f069c on main.

@rajathagasthya rajathagasthya force-pushed the dynamic-mig-config branch 2 times, most recently from 55d4a41 to cc8d164 Compare February 13, 2026 14:53
This change restores static MIG configs due to issues with R535 drivers
not being able to detect MIG profiles. The configmap is volume mounted
onto the MIG manager container as config-default.yaml, so that MIG
manager can fall back to this config whenever generation fails.

Signed-off-by: Rajath Agasthya <ragasthya@nvidia.com>
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.

4 participants