pvarki / pvarki/python-matrix-rmapi
Rewrite the Matrix integration to k8s native and compliant to the new integration sec
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- Avg merge
- 21h 57m
- Merged PRs (30d)
- 1
Description
Whatever the integration does now, make it k8s native and compliant to the new platform integration spec.
- reconcile the integrated product to the cluster's true state (User, Group, Role, UserBinding)
Also implement sanity, get rid of ugly hacks - quality first
Acceptance Criteria
Potentially break this up to multiple tasks.
- (Prerequisite) Kubev2 integration spec is stable enough to do this
- Consider base requirements of the new world, possibly change the integration spec if something's direly needed that is not there already
- Design the new product integration
- 🚢 it
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 checking whether the Kubev2 integration spec is stable, then review the current Matrix integration against the listed User, Group, Role, and UserBinding reconciliation requirements. Done means a designed and shipped integration that is Kubernetes-native, compliant with the new spec, and includes sanity checks without the existing hacks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, python
- Domain
- infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100