cloudfoundry / cloudfoundry/stratos
Support deploying apps from private container registry
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
Detailed Description
Right now, push apps via stratos with docker images from public container registry is possible. It would be great to expand this feature to support pushing apps from private container registry that requires authentication.
Context
Most of the enterprises store their docker images that require access with proper authentication, whether their registry is on public cloud or on premise. It would be benefit to these enterprises to have a handy tool like stratos that complies with their DevSecOps practice or security policy.
Possible Implementation
At a minimum, it should be able to support basic authentication. This behavior should be consistent with the current documented CLI approach
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 reviewing Stratos's existing deployment flow for public container-registry images and the linked Cloud Foundry documentation for private repositories. Identify how registry authentication would fit into that flow; done means apps can be deployed from private registries with at least basic authentication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100