Move from docker-compose to k8s
- Dominant language
- Python
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Very much would need help with this as I am not a k8s fanatic yet. It's important that given the current architecture, we move to k8s properly from docker-compose.
To do for this issue:
- [x] Fix the docker configs
- [x] Make docker-compose to be more image-focused rather than building it from scratch focused.
- [x] Run kompose on the docker-compose file
- [ ] make sure that the everything works on k8s.
Will tackle running the nodes in another issue.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the current Docker configs and docker-compose file, then inspect the manifests generated by kompose. Run the application on Kubernetes and verify that everything works; the issue is done when the existing architecture runs successfully on Kubernetes. Node execution is explicitly deferred to another issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100