pvarki / pvarki/python-rasenmaeher-k8soperator
Kubev2/Spec the integration manifest (MVP)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 5h 2m
- Merged PRs (30d)
- 3
Description
Integration manifest should claim what this integration wants, see the design at https://pvarki.getoutline.com/doc/k8s-crd-design-jKXaCOi2m3)
Design further what it should be. Consider eg MediaMTX as a testbed integration.
Acceptance Criteria
- [ ] Rambo & Siikanen likes it
- We don't need to overspec this now, just a base that is sane and Works™️
- This spec lets us start turning our product integrations K8s-native
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 linked Kubernetes CRD design and use MediaMTX as the proposed testbed integration. Work out the smallest integration manifest that claims an integration's needs and supports moving product integrations toward Kubernetes-native operation. Done means the design is accepted by Rambo and Siikanen and provides a sane, working base without overspecification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, python
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100