openmcp-project / openmcp-project/backlog
Spike: Evaluate if multicluster-runtime solves AccessRequest refresh problem
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Time for it:
2 days
Description
We need to evaluate if the multicluster-runtime could be used to solve the problem #432.
Also needs to be investigated if the kubernetes-graphql-gateway has already a solution which we could use. We need to contact the Platform Mesh team for it.
On Success
Create a task for the PoC implementation of it for one operator:
- project-workspace-operator
- openmcp-operator
- ...
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 reading issue #432 and the multicluster-runtime documentation, then investigate whether kubernetes-graphql-gateway already addresses the AccessRequest refresh problem. Contact the Platform Mesh team for additional context. Done means creating a task for a PoC implementation for one operator, such as project-workspace-operator or openmcp-operator.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100