[Discussion] RC and usvc
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 5
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 10
Description
Discussions to be held:
- What is the relation between the microservices and the run control?
- Do we expect an interface from the run control to the usvcs? (probably not)
- Should there be a simple wrapper around the kubectl commands to simplify the administrative workload, or should this be left entirely in the hands of the sysadmins?
- Could we do something in between, where the run control pings an intermediary servcice or has a set of commands that can interface with the cluster to determine whether the services are alive and well? In doing so, could we build a very simple dashboard that tells us the status of these services?
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
No files, tests, or entry points are named. Start by mapping the existing run-control and microservice boundaries, then examine how kubectl and cluster health are currently handled. Resolve whether the intended outcome is an interface, command wrapper, intermediary health service, or dashboard before defining implementation files and acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, python
- Domain
- backend, devops, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100