redpanda-data / redpanda-data/redpanda
Installing as non-admin in a single kubernetes namespace
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12.6k
- Forks
- 792
- PR merge metrics
- No merged PRs in 30d
Description
Who is this for and what problem do they have today?
I am using a on-prem kubernetes cluster where my team is confined to a single namespace. Currently I cannot install redpanda using the steps at https://docs.redpanda.com/docs/quickstart/kubernetes-qs-cloud/ since I do not have cluster admin privs.
What are the success criteria?
Possibility to install redpanda without being cluster admin.
Why is solving this problem impactful?
Teams can try out redpanda easier without involving local infra staff
Additional notes
We also require all containers to run as non-root users.
JIRA Link: CORE-894
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
Start with the Kubernetes quickstart linked in the issue and review the related CORE-894 JIRA ticket. Determine which installation steps require cluster-admin access and how the deployment can remain within one namespace while running all containers as non-root. Done means the documented installation succeeds without cluster-admin privileges and meets the stated non-root requirement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100