-
This issue is to finalize the names of API resources before moving the service-catalog API to beta.
### Requirements:
- We should not have any name collisions with core resources
- When naming …
-
The current API stores parameters on an instance as a runtime.RawExtension.
It's very likely parameters may actually hold sensitive information, we should think about how to handle these as secrets…
-
Currently, the Instance resource has the following properties that are settable by users:
- PlanName
- Parameters
- ParametersFrom
There is no way for a user to determine what the actual values …
-
We have an example here https://github.com/hchenxa/daily_work/tree/master/kubernetes/service-catalog and want to contribute to service catalog.
Can we put all the works related to MySQL under https…
-
## Problem
*As a service broker author I can choose to ignore CF-isms in the Service Broker API specification and see that these are deprecated, but still available, just not as a top level attrib…
avade updated
7 years ago
-
This issue will be a bucket to hold use cases focused on issues service producers are facing. After we have a solid set we can organize them into a document and review in a sig meeting.
slack updated
7 years ago
-
We have addressed this concern piecemeal in a couple different places, but I think it is advantageous to open a high-level issue for it and explain the rationale in detail.
I propose that we make t…
-
Background:
kubectl and the Kubernetes reference docs both depend on the swagger.json spec to operate on Kubernetes resources. The swagger.json lacks important information required by kubectl and th…
-
The obvious benefit of dropping these two modes is that it frees us to focus efforts on CF mode, Steward's internal state machine, and most importantly the UX.
Benefits aside, I'll try to defend why …
-
**UPDATE:** This proposal is now available as a [slide deck](https://docs.google.com/presentation/d/1Fm3qG9zQ4R8ZbhtTObmQjO3UZYJ0ruYI4qr5w_gEKN8/edit?usp=sharing), complete with diagrams and examples.…