Investigate supporting multiple Atlas credentials per broker deployment
jasonmimick opened this issue · comments
Users trying to manage many Atlas clusters (for example ~200) need a better way to segregate these clusters into different Atlas Projects. There are technical as well as usability issues with using only 1 project (e.g automation update rollouts, Atlas supports only 25 clusters per project).
This ticket tracks the investigation of a possible integrated solution for the Cloud Foundry platform using Cloud Foundry CredHub.
References:
https://github.com/cloudfoundry/secure-credentials-broker
https://tanzu.vmware.com/content/blog/need-to-secure-credentials-for-off-platform-services-in-pcf-try-the-credhub-service-broker-now-in-beta-we-take-an-inside-look
Documenting how this will work, user docs
https://github.com/jasonmimick/atlas-osb/wiki/Multiple-Atlas-project-per-broker
We've moved the latest docs over into the current dev branch:
https://github.com/jasonmimick/atlas-osb/blob/ymlplans/docs/custom-plans.md
This is in order to support better usability by being able to clone all the docs and code from one repository. The wiki pages will be deprecated.
We are doing this in YMLPLANS