fix(drivers): normalize label namespace - #3609
Merged
Merged
Conversation
Signed-off-by: Evan Lezar <elezar@nvidia.com>
elezar
requested review from
a team,
derekwaynecarr,
mrunalp and
sjenning
as code owners
September 23, 2026 12:41
drew
approved these changes
Sep 23, 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
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.
Summary
Normalize driver-owned label keys on the repository's canonical
openshell.ai/namespace. This removes the remainingopenshell.io/labels from the Podman and VM drivers and keeps their selectors, fixtures, E2E helpers, and documentation aligned.Related Issue
No issue required: this is a localized consistency fix for existing driver label keys.
Changes
openshell.ai/isolation-roleopenshell.ai/extension.openshell.io/label keys remainTesting
mise run pre-commitpassescargo test -p openshell-driver-podmancargo test -p openshell-driver-vm lifecycle::testsThe full VM unit suite was also attempted. Its label-related lifecycle tests passed; seven unrelated tests could not complete because local
e2fsprogstools are unavailable or existing tracing fixtures timed out.Checklist