This repository has been archived by the owner on May 6, 2022. It is now read-only.
Implementation of service catalog #37
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is an initial implementation of the service catalog, consisting of three parts. Service Controller The service controller performs the following functionality: - watches for and manages the kubernetes resources in the system - interacts with service brokers - handles consumption of binding credential information Kubernetes Broker The k8s broker is a white-box service broker which supports user-defined service classes implemented in terms of Helm charts. This broker consists of two parts: the broker, which implements the standard Cloud Foundry Service Broker v2 API; and the registry, which provides an API for dynamic management of classes in the broker's catalog. User-provided Service Broker The UPS broker provides the "user-provided-service" service class, which takes as inputs a set of credentials and returns those credentials when being bound to. It is meant to mimic the Cloud Foundry concept of "user-provided service instances" using the standard broker/class model. The authors are: Ville Aikas (@vaikas-google) Brendan Melville (@bmelville) Martin Maly (@martinmaly) Michael Kibbe (@mkibbe1993)
jboyd01
pushed a commit
to jboyd01/service-catalog
that referenced
this pull request
Dec 20, 2018
added eriknelson for review
mszostok
referenced
this pull request
in mszostok/service-catalog
Aug 13, 2019
* Create documentation about rollback * Apply suggestions from code review Co-Authored-By: Klaudia Grzondziel <35192450+klaudiagrz@users.noreply.github.com> * after review
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an initial implementation of the service catalog, consisting
of three parts.
Service Controller
The service controller performs the following functionality:
Kubernetes Broker
The k8s broker is a white-box service broker which supports
user-defined service classes implemented in terms of Helm charts.
This broker consists of two parts: the broker, which implements
the standard Cloud Foundry Service Broker v2 API; and the registry,
which provides an API for dynamic management of classes in the
broker's catalog.
User-provided Service Broker
The UPS broker provides the "user-provided-service" service class,
which takes as inputs a set of credentials and returns those
credentials when being bound to. It is meant to mimic the Cloud
Foundry concept of "user-provided service instances" using the
standard broker/class model.
The authors are:
Ville Aikas (@vaikas-google)
Brendan Melville (@bmelville)
Martin Maly (@martinmaly)
Michael Kibbe (@mkibbe1993)