chore: make windows agent runnable by ContainerUser #1241
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
To improve our security posture for the new Windows integration, the infrastructure agent container that runs in the windows kubelet pod should be runnable by a user with reduced permissions. We can use the virtual user
ContainerUser
rather thanContainerAdministrator
by granting modify permissions toUsers
for the relevant path in the infra agent Docker file & removing theemptyDir
mount path for the\tmp
directory. Agent code deletes this directory during startup, which can apparently be done by theContainerAdministrator
but not theContainerUser
no matter how many permissions you give it. The agent will manage creating the directory itself.Skip Changelog label added due to unrelease feature.
Type of change
Checklist: