Koenkk / Koenkk/zigbee2mqtt-chart
Security Context violates the PodSecurity baseline
Open
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 37
- Forks
- 24
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 2
Description
Security Context violates the PodSecurity baseline #52
Warning FailedCreate 70s (x15 over 2m32s) statefulset-controller create Pod zigbee2mqtt-0 in StatefulSet zigbee2mqtt failed error: pods "zigbee2mqtt-0" is forbidden: violates PodSecurity "baseline:latest": non-default capabilities (container "zigbee2mqtt" must not include "SYS_ADMIN" in securityContext.capabilities.add), privileged (container "zigbee2mqtt" must not set securityContext.privileged=true)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start at the StatefulSet's Helm securityContext configuration and compare the zigbee2mqtt container settings with the PodSecurity baseline requirements; done means the StatefulSet can create its pod without the reported SYS_ADMIN or privileged violations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100