-
Notifications
You must be signed in to change notification settings - Fork 28
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
K8S Platform Specific Deployment for Service Broker Proxy module #29
Comments
Service Catalog will support namespace scoped brokers: kubernetes-retired/service-catalog#1826 |
I thought we are not planning support for space scoped brokers in the CF scenario (meaning space scoped brokers registration is not managed by Service Manager). Doesn't this imply that we shouldn't be concerned with namespace registered brokers in the K8S scenario ? |
The K8S namespace scope is quite different from CF scoped brokers. |
ok, makes sense then :) |
Background
Service Broker Proxy need to be deployed on all platforms that want to use Service Manager.
We need to provide packages that allow deployment on K8S and CF as host platforms for Service Broker Proxy module.
The implementation is separated on 2 parts:
Service Broker Proxy Core module - that take cares for Business logic implementation including:
Platform specific module - that take cares for packaging and platform specific configuration like:
Example with Go Application packaging for K8S can be seen on:
https://github.com/kubernetes/examples/tree/master/guestbook-go
Easy of deployment that is good to achieve is like following:
https://github.com/kubernetes/dashboard/releases
An yaml file that have all configurations needed inside:
https://github.com/kubernetes/dashboard/blob/master/src/deploy/recommended/kubernetes-dashboard.yaml
Objective
Prepare K8S Platform dependent module.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: