mayadata-io / mayadata-io/d-operators
use case: use dope as a binary scoped to a kubernetes namespace
Open
Nobody has claimed this yet.
config
dev persona
namespace
use case
- Dominant language
- Go
- Stars
- 10
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
ProblemStatement: As a developer I want to use dope as a simple binary to manage my use cases. I want to make use of the custom resources exposed by dope without the need to modify the cluster. I am restricted to run my use cases within the namespace allocated to me.
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 by reviewing the dope binary entry point and how it currently accesses Kubernetes custom resources. Determine the namespace-scoped behavior required for running without cluster modification, then define acceptance checks showing that use cases can be managed within the allocated namespace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100