Support optional non-root transport trust installation
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 218
- Forks
- 72
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 427
Description
Description
Support running the transport trust-bundle installer as non-root in Kubernetes namespaces that enforce the Restricted Pod Security Standard.
This is optional hardening. It is not required to complete PKI Epic #19 or the end-to-end validation in #52. The current installer behavior remains supported while this follow-up is open.
Definition of Done
- The optional non-root path makes the merged certificate volume writable by the
nvca-trust-inituser. - That path does not require UID 0 or
runAsNonRoot: false. - Tests cover the current behavior and pods that already enforce a non-root security context.
- Restricted Pod Security validation passes when the optional path is selected.
Tracking
This issue is not a native sub-issue of #19 and does not gate epic closure.
Contributor guide
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 files or tests are named; start by locating the transport trust-bundle installer and its merged certificate volume setup, then inspect existing security-context tests. Done means the optional path permits non-root writes without UID 0 or runAsNonRoot: false, preserves current behavior, covers both contexts, and passes Restricted Pod Security validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100