search

vmware-tanzu / kubeapps

A web-based UI for deploying and managing applications in Kubernetes clusters
Other
4.92k stars 708 forks source link

Question about kubeapps/service catalog #2125

Closed obeyler closed 3 years ago

obeyler commented 3 years ago

Service Catalog integration has been removed from kubeapps 2.0.0 we used it to share different service on differents K8S and on Cloudfoundry Do you plan to add it again ?

absoludity commented 3 years ago

Context from the slack discussion.

We weren't planning to add it back in its current form, as Andres mentioned. Google moved GCP to Config Connector, while AWS seems to be moving towards Amazon Controllers for Kubernetes, both of which are providing paths for creating and connecting to their catalog of services from K8s. We're following these as they mature.

You can still install the service catalog chart and make the services available via the kubectl CLI so they can be shared, I think? But we're probably missing part of your use-case... can you expand a bit on how you're using Kubeapps with the service broker support, as from what you've said, it sounds like you're only using it as a UI to provision service instances - not sure?

gberche-orange commented 3 years ago

thanks @absoludity for considering service catalog use-cases from the community.

Many OSB services brokers for on-prem services (operated outside of K8S) are currently used by the community in production and also need to be provisionned using svcat for use by applications operated in K8S, and would benefit from a web ui for this. Following are example of such community service brokers:

Regarding public cloud providers, I understand GCP and AWS operators still don't have parity with the corresponding service brokers:

Google moved GCP to Config Connector, while AWS seems to be moving towards Amazon Controllers for Kubernetes, both of which are providing paths for creating and connecting to their catalog of services from K8s. We're following these as they mature.

The GCP service broker provides provisionning support for many resources that Config Connector does not seem to yet support as of Nov 12, 2020. GCP Service Broker provides additional support for:

The aws-controllers-k8s status is mostly preview as of Nov 12, 2020: image

The awslabs/aws-servicebroker supports

absoludity commented 3 years ago

@gberche-orange Thanks for providing more details. Our main difficulty was that we were only 2 people working on the Kubeapps team and didn't have the capacity to maintain everything while moving forward with new features. @andresmgot worked on the service broker support when it was originally added and may have more details, but he'd mentioned on slack that we were thinking about deprecating it back in July, but we could have made a wider request so that we had your input earlier.

That said, there's nothing stopping us putting the code back if there's both good reason to as well as resources available to maintain it, but we are still a very small team. Is there a possibility that your team could provide an engineer to help? We'll look over the details next week and perhaps then discuss it in our next planning meeting, which you're welcome to join - details in the slack topic.

gberche-orange commented 3 years ago

thanks @absoludity for your prompt response. I'm sorry our team did not properly voiced OSB community use-cases earlier back in July.

I fully understand (and experience...) engineering resource constraints as well as necessary product prioritization in open source projects. Our team has unfortunately no front-end skills so we won't be able to help with kubeapps engineering :-(

I wonder whether vmware tanzu product teams are actually leveraging closed-source service-catalog ui for exposing their OSB-based managed services (such as within Tanzu Mission Control or vsphere 7 custom UIs ) or could instead contribute opensource service catalog support in KubeApps or another K8S UI such as octant as octant-plugin

Besides, we're studying with the Suse team whether service catalog support in the Stratos Cloudfoundry and K8S UI could make sense. In particular, whether it would be possible to share the same front-end code between K8S service-catalog support and Cloudfoundry service marketplace (in order to factor our maintenance effort in the long run). I'll update this issue with the related feature request in the stratos repo so that both projects can follow each other directions on this topic.

ppbaena commented 3 years ago

This issue had no activity for a long time; in order to focus on the current roadmap, we are closing this issue. Should anyone be interested in contributing or have any further questions, please reopen it.

Thanks for your comprehension