Skip to content

fix: map ids per pod correctly in kubelet-config - #1060

Merged
ginglis13 merged 1 commit into
bottlerocket-os:developfrom
rose-m:fix/correct-ids-per-pod-setting
Sep 24, 2026
Merged

ginglis13 merged 1 commit into
bottlerocket-os:developfrom
rose-m:fix/correct-ids-per-pod-setting

Conversation

@rose-m

@rose-m rose-m commented Sep 24, 2026

Copy link
Copy Markdown
Contributor

Description of changes:

The actual KubeletConfiguration property is userNamespaces.idsPerPod as shown here:
https://kubernetes.io/docs/concepts/workloads/pods/user-namespaces/#id-count-for-each-of-pods

It was previously mapped to a root-level idsPerPod key which did not have any effect.

Testing done:

Terms of contribution:

By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.


Happy to follow up with additional changes where needed - thank you!

The actual KubeletConfiguration property is `userNamespaces.idsPerPod`
as shown here:
https://kubernetes.io/docs/concepts/workloads/pods/user-namespaces/#id-count-for-each-of-pods

It was previously mapped to a root-level `idsPerPod` key which did not
have any effect.
@ginglis13

Copy link
Copy Markdown
Contributor

LGTM, thanks @rose-m

@ginglis13
ginglis13 merged commit 3521fc3 into bottlerocket-os:develop Sep 24, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants