revert: Remove g7e MIG profiles (hold back MIG support for RTX PRO 6000)#403
Merged
mollyheamazon merged 1 commit intoaws:mainfrom Apr 7, 2026
Merged
Conversation
Remove MIG-specific configuration for g7e instances while keeping instance type recognition and hardware specs intact: - Remove g7e entries from INSTANCE_TYPE_MIG_PROFILES in constants.py - Remove g7e MIG config block from GPU operator default-mig-config.yaml g7e instances remain valid for HyperPod CLI operations in whole-GPU mode. MIG partitioning will be re-enabled in a future PR. Partially reverts: 902e88f (PR aws#390), fully reverts MIG portion of 51b342f (PR aws#391)
PremiumSpider
requested a deployment
to
manual-approval
GitHub Actions
Waiting
mollyheamazon
approved these changes
Apr 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What's changing and why?
Why now: The g7e MIG profiles (PRs #390, #391) merged to main on Mar 19 but haven't shipped yet (latest release is v3.7.0 from Mar 2). If we release without reverting, customers would see
MIG profiles for g7e via list-accelerator-partition-type and attempt to use them before MIG on RTX PRO 6000 is fully validated end-to-end. This revert prevents exposing unvalidated MIG
functionality while keeping g7e fully usable in whole-GPU mode.
Removing MIG-specific configuration for g7e instances to decouple MIG support
from the initial g7e release. Instance type recognition and hardware specs
remain intact so g7e clusters work in whole-GPU mode.
Changes:
default-mig-config.yaml
Partially reverts 902e88f (PR #390), fully reverts MIG portion of 51b342f (PR #
391). MIG partitioning for g7e will be re-enabled in a future PR.
Before/After UX
Before: g7e instances support MIG partitioning with profiles 1g.24gb, 2g.48gb,
4g.96gb.
After: g7e instances work in whole-GPU mode only. MIG configuration requests for
g7e are rejected by the CLI. All other instance types' MIG configs are
unaffected.
How was this change tested?
Config-only removal. Verified:
access — no KeyError risk
Are unit tests added?
N/A — config-only change (removal of entries).
Are integration tests added?
N/A — config-only change.
Reviewer Guidelines
justification.
release support for g7e