defenseunicorns / defenseunicorns/uds-cli
uds-compose command that is similar to docker-compose
- Dominant language
- Go
- Stars
- 54
- Forks
- 21
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 45
Description
### Is your feature request related to a problem? Please describe
Enable developers the ability to quickly deploy code under development into an image and that image into a local cluster that mimics Production configuration but all local to their machine and ideally without the need for root permissions to a Docker.
### Describe the solution you'd like
Developers need to be able to deploy a cluster locally, deploy their app and any dependencies. This would help simulate deployment to a Production environment but on the devs local machine for ease of dev/test. This concept is similar to docker-compose. Stretch goals would be to autodetect changes and deploy the app to a local cluster or have one command similar to the uds-core model "uds run dev-deploy --set PKG=metrics-server"
Goal is to use rootless-podman to simulate/eliminate the need/dependency on root or docker socket. Running a kind cluster on rootless podman with uds deployed has been demonstrated in [kind cluster/rootless podman](https://gitlab.devops.nswccd.navy.mil/project-blue/defense-unicorns/shipmates/uds/uds-kind/-/issues/1). This ticket should focus on the dev workflow. The networking/port forwarding giving the devs access to apps need to be investigate. Currently uds dev port fowards to 80/80 and 443/443.
### Describe alternatives you've considered
Docker-Compose
(optional) A clear and concise description of any alternative solutions or features you've considered.
### Additional context
Add any other context or screenshots about the feature request here.
Contributor guide
Research direction
Start with the existing `uds dev` port-forwarding behavior and the `uds run dev-deploy --set PKG=metrics-server` workflow; review the linked kind/rootless-Podman demonstration. Done means a defined, rootless local-cluster workflow can deploy an app and dependencies with the required local networking, but this issue does not name files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kubernetes
- Domain
- cli, developer-experience, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100