When a Broker is created, the broker control loop calls the CF service broker API at the Broker's specified host information, converts all responses to a list of ServiceClasses, and writes them all to Kubernetes. The API should allow for running each ServiceClass through a caller-specified filter before writing them to Kubernetes, so service catalog controller creators can opt out of services they don't want published.
When a
Brokeris created, the broker control loop calls the CF service broker API at theBroker's specified host information, converts all responses to a list ofServiceClasses, and writes them all to Kubernetes. The API should allow for running eachServiceClassthrough a caller-specified filter before writing them to Kubernetes, so service catalog controller creators can opt out of services they don't want published.Moved from https://github.com/deis/steward/issues/128