rancher / rancher/support-bundle-kit
Security context of supportbundle-agent deamonset is not exposed
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 43
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 6
Description
When consuming this project and extent the sript to collect more nodes information, some commandline (eg iptable) needs higher privilege, while the securityContext is hardcoded in go code see
https://github.com/rancher/support-bundle-kit/blob/master/pkg/manager/agent.go#L85
Is it possible to expose Security context of supportbundle-agent deamonset as a parameter ?
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
Start in pkg/manager/agent.go around line 85, where the supportbundle-agent DaemonSet securityContext is hardcoded. Trace how the agent configuration is constructed and identify where a security-context parameter could be passed through; done means consumers can configure that DaemonSet securityContext instead of using only the hardcoded value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100