pvarki / pvarki/python-rasenmaeher-k8soperator
Design the RASENMAEHER v2 REST API
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 5h 2m
- Merged PRs (30d)
- 3
Description
The rest api will create users and other things as k8s resources. Those resources will be the reality for rmk8soperator who will reconcile integrations to this new reality once it learns something has changed.
Other things: Consider what integrations really need.
Acceptance criteria
- [ ] The rest api lives under rmk8s repo
- The api considers what we actually need here
- Sane enough so that we can do a MVP and hopefully don't have to instantly release a /v2/ after that, i.e. done elegantly. Axe features instead of elegantness at this point
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 reading the rmk8s repo, including its Kubernetes Operator and CRDs, to understand the resources the API must create and the integrations that depend on them. Define the smallest MVP API that creates users and other required Kubernetes resources, then verify that the API lives under the rmk8s repo and meets the stated acceptance criteria without requiring an immediate v2.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, python
- Domain
- api, backend, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100