Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve developer workflow so pushed APBs are restricted to private namespace #254

Open
jwmatthews opened this issue Apr 2, 2018 · 1 comment

Comments

@jwmatthews
Copy link
Contributor

This RFE requires namespace ClusterServiceClasses to be supported in the Service Catalog. That work is actively being developed in sig-service-catalog and expected to be in upstream perhaps in ~next month or two.

Once the ability to publish ClusterServiceClasses to a particular namespace is popular we should document a workflow of leveraging this so a developer working on a shared remote cluster is able to push their own APBs for testing without impacting others.

@eriknelson
Copy link
Contributor

Just providing some additional context: as long as the namespaced broker is configured to discovered these namespaced APBs, any services reported to the catalog will automatically be created as ServiceCatalog objects, scoped and deployable to that namespace, without impacting other tenants.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants