stackabletech / stackabletech/issues
Client/gateway functionality
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
As a user of the products in the SDP I'd like an easy way to access and use the deployed products.
An idea on how this could look like:
- We provide a UI (web interface but stackablectl could also be an option) where a user selects a namespace and/or deployed products of Stackable
- Our tool then builds a Dockerfile which will pull in the product images (all versions should already be in the docker repo because they have been deployed) and does a multi-stage build using those products plus a "base" client image to build one master image that contains all of that
- The tool also builds a Pod YAML that pulls in this image plus the relevant ConfigMaps
- Optional: Our tool also builds the image and pushes it to a repo (needs permissions)
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 source files or tests are named. Start by clarifying whether the interface should be a web UI, stackablectl, or both, then map the required namespace and deployed-product inputs to the Dockerfile and Pod YAML outputs described here. Done should include a defined workflow for producing the image and deployment YAML, with image pushing treated as an optional permission-dependent step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100