oskoperator / oskoperator/osko
Better Authorization
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 20
- Forks
- 3
- Avg merge
- 44m
- Merged PRs (30d)
- 7
Description
Currently the namespace-scoped CRD allows reference to secrets in other namespaces, which may enable namespace-scoped users to access secrets in unauthorized namespaces. Perhaps it's better to add webhooks to authorize users before referencing secrets.
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 by tracing how the namespace-scoped CRD references secrets across namespaces and where authorization is currently enforced. Review the Kubernetes webhook entry points and related CRD handling; done means unauthorized cross-namespace secret references are rejected while permitted references continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- authorization, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100