Service Broker create error

Couchbase Server Kubernetes
1

Fresh install of 2.2 operator and 1.1 service broker, following the Getting Started.
Service operator create fails as below after running prior commands that set up crd’s:
Anybody got thoughts?

./cbsbctl create servicebroker --profile demo
clusterroles/couchbase-service-broker created
servicebrokerconfigs/couchbase-service-broker created
serviceaccounts/couchbase-service-broker created
rolebindings/couchbase-service-broker created
secrets/couchbase-service-broker created
deployments/couchbase-service-broker created
services/couchbase-service-broker created
**Error: unable to get rest mapping for kind ServiceBroker.servicecatalog.k8s.io: no matches for kind "ServiceBroker" in version "servicecatalog.k8s.io/v1beta1"**
Usage:
  cbsbctl create servicebroker [flags]

Flags:
  -h, --help   help for servicebroker

Global Flags:
      --as string                      Username to impersonate for the operation
      --as-group stringArray           Group to impersonate for the operation, this flag can be
2

That’s because you haven’t installed the service catalog, which the service broker is designed to use.

3

I had missed that step, but after installing the service catalog, I still get the error:
Error: unable to get rest mapping for kind ServiceBroker.servicecatalog.k8s.io: no matches for kind “ServiceBroker” in version “servicecatalog.k8s.io/v1beta1”

and I confirmed that the crd.yaml had been run for service broker

4

Can you confirm that kubectl get crd output doesn’t contain that resource type/version? You may need for it to actually be created and registered before provisioning.

5

it does not, here’s the relevant part of the list
runtasks.openebs.io 2021-06-19T10:52:55Z
servicebrokerconfigs.servicebroker.couchbase.com 2021-06-19T10:26:23Z
servicemonitors.monitoring.coreos.com 2021-06-19T09:52:19Z

I see the one above n the crd…I don’t see 'ServiceBroker.servicecatalog.k8s.io" as in the error message.

6

If I run

helm install --wait --repo https://kubernetes-sigs.github.io/service-catalog --namespace default catalog catalog --version 0.3.1

I see the following almost instantly

kubectl get crd
NAME                                          CREATED AT
clusterservicebrokers.servicecatalog.k8s.io   2021-06-28T11:29:29Z
clusterserviceclasses.servicecatalog.k8s.io   2021-06-28T11:29:29Z
clusterserviceplans.servicecatalog.k8s.io     2021-06-28T11:29:29Z
servicebindings.servicecatalog.k8s.io         2021-06-28T11:29:29Z
servicebrokers.servicecatalog.k8s.io          2021-06-28T11:29:29Z
serviceclasses.servicecatalog.k8s.io          2021-06-28T11:29:29Z
serviceinstances.servicecatalog.k8s.io        2021-06-28T11:29:29Z
serviceplans.servicecatalog.k8s.io            2021-06-28T11:29:29Z

I’d check that you have the right version of the chart installed, and if that doesn’t work out, then contact the service catalog team as they’re the technical experts in this!

7

My local repo was corrupt, once I removed that I was able to install the service catalog and successfully do the

./cbsbctl create servicebroker --profile demo

On to the next step, thanks for your help @simon.murray