search

kubernetes-retired / service-catalog

Consume services in Kubernetes using the Open Service Broker API
https://svc-cat.io
Apache License 2.0
1.05k stars 384 forks source link

Implement a naming strategy that gives service classes and plans human readable names #1950

Closed pmorie closed 2 years ago

pmorie commented 6 years ago

When we were trying to deal with name mutability in https://github.com/kubernetes-incubator/service-catalog/issues/802, we decided to use the OSB IDs of services and plans as the k8s names to deal with mutability. This results in a very clunky (basically unusable) kubectl experience because the k8s names are not easily distinguishable. The svcat tool makes this easier to manage, but not every user wants to download and use another tool.

Luckily, we also left ourselves space to implement alternate naming strategies for service classes and plans. I think we should implement an (optional, opt-in) naming strategy that:

To be super-clear, we will have to maintain the existing behavior of the system. We should allow administrators to decide on this behavior by adding a field to the broker resources that controls the naming strategy, and which defaults to the existing behavior. For example:

metadata:
  name: my-broker
spec:
  url: http://my.broker.to
  namingStrategy: HumanReadable

We discussed this as something people were interested in for 1.0.0 at the april f2f.

n3wscott commented 6 years ago

This is related: https://github.com/openservicebrokerapi/servicebroker/pull/504

fejta-bot commented 5 years ago

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

fejta-bot commented 5 years ago

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

fejta-bot commented 5 years ago

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

mszostok commented 5 years ago

/remove-lifecycle rotten /lifecycle frozen

mrbobbytables commented 2 years ago

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