feat: persist ENABLE_MANAGED_GPU_EXPERIENCE state as a marker file on disk#7952
Merged
ganeshkumarashok merged 2 commits intomainfrom Feb 27, 2026
Merged
feat: persist ENABLE_MANAGED_GPU_EXPERIENCE state as a marker file on disk#7952ganeshkumarashok merged 2 commits intomainfrom
ganeshkumarashok merged 2 commits intomainfrom
Conversation
surajssd
requested review from
AbelHu,
Devinwong,
YaoC,
awesomenix,
calvin197,
cameronmeissner,
djsly,
ganeshkumarashok,
juan-lee,
junjiezhang1997,
lilypan26,
mxj220,
pdamianov-dev,
phealy,
r2k1,
timmy-wright,
yewmsft and
zachary-bailey
as code owners
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds a marker file /opt/azure/containers/managed-gpu-experience.enabled to persist the managed GPU experience state, allowing other node components to discover whether the feature is enabled. The implementation follows the established marker file pattern (e.g., provision.complete, base_prep.complete).
Changes:
- Added marker file creation/deletion in
configureManagedGPUExperience()function - Updated unit tests to mock and verify
mkdir,touch, andrmcommands - Regenerated test snapshots (gzipped CustomData) to reflect the updated script
Reviewed changes
Copilot reviewed 33 out of 67 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| parts/linux/cloud-init/artifacts/cse_config.sh | Added marker file logic with directory creation and file touch/removal |
| spec/parts/linux/cloud-init/artifacts/cse_config_spec.sh | Added mocks for mkdir, touch, rm and test assertions |
| pkg/agent/testdata/*/CustomData | Regenerated gzipped cloud-init data snapshots |
awesomenix
approved these changes
Feb 25, 2026
surajssd
force-pushed
the
suraj/persist-managed-gpu-exp-flag
branch
from
1ca73b3 to
a4d4d88
Compare
… disk Allow other node components to discover whether managed GPU experience is enabled by writing /opt/azure/containers/managed-gpu-experience.enabled on enable and removing it on disable, following the established marker file pattern (e.g. provision.complete). Signed-off-by: Suraj Deshmukh <suraj.deshmukh@microsoft.com>
surajssd
force-pushed
the
suraj/persist-managed-gpu-exp-flag
branch
from
a4d4d88 to
fde33b1
Compare
ganeshkumarashok
approved these changes
Feb 27, 2026
saewoni
pushed a commit
that referenced
this pull request
Mar 20, 2026
… disk (#7952) Signed-off-by: Suraj Deshmukh <suraj.deshmukh@microsoft.com>
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
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.
Allow other node components to discover whether managed GPU experience
is enabled by writing /opt/azure/containers/managed-gpu-experience.enabled
on enable and removing it on disable, following the established marker
file pattern (e.g. provision.complete).