Skip to content
This repository has been archived by the owner on May 6, 2022. It is now read-only.

Meta: Use case documentation #20

Closed
pmorie opened this issue Oct 25, 2016 · 17 comments
Closed

Meta: Use case documentation #20

pmorie opened this issue Oct 25, 2016 · 17 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. meta
Milestone
1.0.0

Comments

@pmorie
Copy link
Contributor

pmorie commented Oct 25, 2016

As discussed in the 20161024 SIG meeting, we should finalize the use cases for the v1 milestone of service catalog.

Use cases articulated during the meeting:

  1. Adding service brokers into catalog
  2. Catalog curation: which broker-provided services are globally visible?
  3. Catalog curation: which namespaces can see which catalog services?
  4. As a consumer of a service, how do I indicate that I want to consume a particular service?
  5. As a consumer of a service, how do I indicate that I want to bind to an instance of a service?
  6. What is the unit of consumption of a service? Namespace? Pod? Something else? (brian to comment)
  7. What is the versioning and update story for a service: example: what happens when a broker changes the services it provides?
  8. When a user binds to an instance of a service, what does that look like? Which resources are created in their namespace?
  9. What is the update story for bindings to a service instance?
  10. How does the catalog support multiple consumers in different Kubernetes namespaces of the same instance of a service?
  11. How do I control the number and identity of consumers allowed to bind to my instance?
  12. Curation: how do I control who can see a service instance that I have provisioned?
  13. Curation: how do I control the number of consumers of my service instance?
@westonh
Copy link

westonh commented Oct 25, 2016

As an addendum to 1. Is there an auth story for adding service brokers? Presumably yes since we want to support private catalogs.

@pmorie
Copy link
Contributor Author

pmorie commented Oct 25, 2016

Arguably most important, as @bgrant0607 pointed out in his post to the mailing list, what does consuming a service look like to a user?

@westonh
Copy link

westonh commented Oct 25, 2016

A few others:

  • Does my catalog list not only my service types but also my instances? E.g., I have a dev cluster running on my local machine and I want to connect my application with a database that exists in a test cluster. How do I find that database instance?
  • Importing a list of brokers: If I have a remote cluster with a service controller that has n brokers registered, how can I import those into my local cluster? Related to the above, can I export a list of service brokers and types from my service controller?

@slack
Copy link
Contributor

slack commented Oct 25, 2016 •
edited

Would it be helpful to group these use cases? Something like:

Catalog Publishing/Curation/Discovery

  • (@pmorie/1) Adding service brokers into catalog
  • (@pmorie/2) Catalog curation: which broker-provided services are globally visible?
  • (@pmorie/3) Catalog curation: which namespaces can see which catalog services?
  • (@slack) How are services identified: name, service name/id, plan name/id?
  • (@westonh) Does my catalog list not only my service types but also my instances?
    • E.g., I have a dev cluster running on my local machine and I want to connect my application with a database that exists in a test cluster. How do I find that database instance?
  • (@westonh) Importing a list of brokers: If I have a remote cluster with a service controller that has n brokers registered, how can I import those into my local cluster?
  • (@westonh) Cann I export a list of service brokers and types from my service controller?
  • (@westonh) Is there an auth story for adding service brokers?

Requesting Services (Consumer)

  • (@pmorie/4) As a consumer of a service, how do I indicate that I want to consume a particular service?
  • (@pmorie/5) As a consumer of a service, how do I indicate that I want to bind to an instance of a service?
  • (@pmorie/10) How does the catalog support multiple consumers in different Kubernetes namespaces of the same instance of a service?

Provisioning/Deprovisioning

  • (@pmorie/13) Curation: how do I control the number of consumers of my service instance?

Binding/Unbinding

  • (@pmorie/8) When a user binds to an instance of a service, what does that look like? Which resources are created in their namespace?
  • (@pmorie/11) How do I control the number and identity of consumers allowed to bind to my instance?
  • (@pmorie/12) Curation: how do I control who can see a service instance that I have provisioned?

Using the Service (Consumption)

  • (@pmorie/6) What is the unit of consumption of a service? Namespace? Pod? Something else? (brian to comment)

Lifecycle of Service

  • (@pmorie/9) What is the update story for bindings to a service instance?
  • (@pmorie/7) What is the versioning and update story for a service: example: what happens when a broker changes the services it provides?

@westonh
Copy link

westonh commented Oct 25, 2016

+1, this is great.

@slack slack mentioned this issue Oct 26, 2016
Merged
@slack
Copy link
Contributor

slack commented Oct 26, 2016

Comments on this issue have been folded into #23.

@pmorie pmorie reopened this Oct 27, 2016
@pmorie
Copy link
Contributor Author

pmorie commented Oct 27, 2016

Reopening, because I think there is another set of use-cases we haven't talked through: use-cases for producing services (ie, how do I run my own service broker)

@bgrant0607
Copy link

@pmorie Aren't we just focusing on consumption of blackbox services at this point?

@pmorie pmorie added this to the MVP 1 milestone Jan 11, 2017
@pmorie
Copy link
Contributor Author

pmorie commented Mar 1, 2017

Someone needs to take a pass back through this stuff and make sure it's done. I believe it is, but I don't have time to check at the moment. I'm going to move this to MVP 2 because it really needs to be done before Kubecon, not at MVP 1.

@pmorie pmorie modified the milestones: MVP 2, MVP 1 Mar 1, 2017
@pmorie pmorie modified the milestones: MVP 3, MVP 2 Mar 9, 2017
@arschles arschles modified the milestones: 0.0.3, 0.0.2 Apr 5, 2017
@arschles arschles changed the title Finish use case documentation Meta: Finish use case documentation Apr 13, 2017
@arschles arschles changed the title Meta: Finish use case documentation Meta: Use case documentation Apr 13, 2017
@arschles
Copy link
Contributor

I have designated this a meta issue and removed it from a milestone

@arschles arschles removed this from the 0.0.3 milestone Apr 13, 2017
@arschles arschles added the meta label Apr 13, 2017
@duglin duglin added this to the 1.0.0 milestone Jul 9, 2017
jeffvance pushed a commit to jeffvance/service-catalog that referenced this issue Sep 1, 2017
@copejon
Merge pull request kubernetes-retired#20 from jeffvance/s3-wip
4612666 
s3-broker port correctly retrieved
jboyd01 pushed a commit to jboyd01/service-catalog that referenced this issue Aug 28, 2018
@openshift-merge-robot
Merge pull request kubernetes-retired#20 from jboyd01/v0.1.29-rebase-…
4007468 
…master

V0.1.29 rebase master
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 21, 2019
piotrmiskiewicz pushed a commit to piotrmiskiewicz/service-catalog that referenced this issue May 15, 2019
Replace tableconvertor with APC (kubernetes-retired#20)
07eb27d
mszostok referenced this issue in mszostok/service-catalog May 16, 2019
@mszostok
Replace tableconvertor with APC (#20)
efc7657
mszostok referenced this issue in mszostok/service-catalog May 16, 2019
@mszostok
Replace tableconvertor with APC (#20)
e8507f5
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 21, 2019
@jberkhahn jberkhahn removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label May 23, 2019
piotrmiskiewicz pushed a commit to piotrmiskiewicz/service-catalog that referenced this issue Jun 12, 2019
@mszostok
Replace tableconvertor with APC (kubernetes-retired#20)
a200440
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 21, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 20, 2019
@mszostok
Copy link
Contributor

/remove-lifecycle rotten
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Sep 20, 2019
k8s-ci-robot pushed a commit that referenced this issue Sep 20, 2019
@mszostok @k8s-ci-robot
Replaces the Aggregated API Server with the CustomResourceDefinitions…
ccab523 
… (CRDs) solution (#2630)

* Add basic validation to crds

* Add webhook skeleton, remove api-server from chart, add webhoook server in chart, move PrepareForCreate login into webhook handler (#2)

* Add webhook skeleton, remove api-server from chart, add webhoook server in chart, move PrepareForCreate login into webhook handler

* Add logger and GVK matcher

* Add test coverage for webhook (#6)

* Add Status entry initialization in binding and instance controller (#5)

* Change fs to label selector (#9)

* Fix removing finalizer after switching to CRD /status sub-resource (#8)

* Add tests to webhooks (#11)

* Replace changevalidator with webhook (#14)

* Replace default service plan with webhook (#10)

* Add tests to webhooks - fix

* Rewrite defaultServicePlan feature to webhook

* Replace plugins by webhook (#16)

* Replace ServiceBinding plugin by webhook

* Replace Broker plugins by webhook

* Adjust webhooks to multi validation handlers

* Service Catalog going towards to CRDs (#18)

* Migrate registry/strategy Updates to webhooks (#17)

* Use Update instead of updateReference method (#19)

* Replace tableconvertor with APC (#20)

* Fix svcat tests after the rebase with the upstream master branch

* Pre delete jobs - remove CRD after delete helm release (#21)

* Apply fixes after executing `make verify`

* Create docs about webhook implementation (#24)

* Change the securePort for the webhook server because colidates with old api-server

* Change import paths to kubernetes-sigs, and rebase with master

* Apply fixes after rebase

Fixes:
* makefile targets,
* instance deprovision operation
* entries under additionalPrinterColumns in crds.yaml
* unit tests after rebase

* Update documentation (#40)

* Update docs

* Fix vendor after rebase with k8s 1.15 bump

* Apply changes after review

- remove the contrib/hack/crd folder
- remove reference to Kyma project
- rebase with current master
- restore the image in chart
- extract CRDs defintion to dedicated folder
@mrbobbytables
Copy link

This project is being archived, closing open issues and PRs.
Please see this PR for more information: kubernetes/community#6632

/close

@k8s-ci-robot
Copy link
Contributor

@mrbobbytables: Closing this issue.

In response to this:

This project is being archived, closing open issues and PRs.
Please see this PR for more information: kubernetes/community#6632

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. meta
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests