fix(vm): create network interfaces with deckhouse user#2430
Merged
Conversation
Signed-off-by: Yaroslav Borbat <yaroslav.borbat@flant.com>
2efef1c to
2583ba6
Compare
LopatinDmitr
approved these changes
Jun 2, 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.
Description
Add
UIDandGIDfields toInterfaceSpec, set to deckhouse user (64535) for all VM network interfaces.Why do we need it, and what problem does it solve?
Tap devices were created with root ownership, causing permission issues for deckhouse user processes. Setting UID/GID explicitly fixes this.
What is the expected result?
VM network interfaces are created with deckhouse user ownership (UID/GID 64535).
Checklist
Changelog entries