Instructions for installing Service Catalog on a Cluster.

Edit This Page


Starting from version 0.3.x, Service Catalog uses Admission Webhooks to manage custom resources. It uses Additional Printer Columns so you can use kubectl to interact with Service Catalog.

The rest of this document details how to:

Step 1 - Prerequisites

Kubernetes Version

Service Catalog requires a Kubernetes cluster v1.13 or later. You’ll also need a Kubernetes configuration file installed on your host. You need this file so you can use kubectl and helm to communicate with the cluster. Many Kubernetes installation tools and/or cloud providers will set this configuration file up for you. Please check with your tool or provider for details.

kubectl Version

Most interaction with the service catalog system is achieved through the kubectl command line interface. As with the cluster version, Service Catalog requires kubectl version 1.13 or newer.

First, check your version of kubectl:

kubectl version

Ensure that the server version and client versions are both 1.13 or above.

If you need to upgrade your client, follow the installation instructions to get a new kubectl binary.

For example, run the following command to get an up-to-date binary on Mac OS:

curl -LO$(curl -s
chmod +x ./kubectl

In-Cluster DNS

You’ll need a Kubernetes installation with in-cluster DNS enabled. Most popular installation methods will automatically configure in-cluster DNS for you:


Service Catalog uses CRDs to store information.


You’ll install Service Catalog with Helm, and you’ll need v3.4.0 or newer for that. See the steps below to install.

Helm Repository Setup

Service catalog uses OCI to store charts. Here are two OCI addresses, which store testing and stable versions respectively.


Your Kubernetes cluster must have RBAC enabled to use Service Catalog.

Like in-cluster DNS, many installation methods should enable RBAC for you.


When using Minikube v0.25 or older, you must run Minikube with RBAC explicitly enabled:

minikube start --extra-config=apiserver.Authorization.Mode=RBAC

When using Minikube v0.26+, run the following command:

minikube start

With Minikube v0.26+, do not specify --extra-config. The flag has since been changed to --extra-config=apiserver.authorization-mode and Minikube now uses RBAC by default. Specifying the older flag may cause the start command to hang.


If you are using the hack/ script in the Kubernetes core repository, start your cluster with this command:


Cloud Providers

Many cloud providers set up new clusters with RBAC enabled for you. Please check with your provider’s documentation for details.

Step 2 - Install Service Catalog

Now that your cluster and Helm are configured properly, installing Service Catalog is simple:

helm install catalog drycc/catalog --namespace catalog --create-namespace

Installing the Service Catalog CLI

Follow the appropriate instructions for your operating system to install svcat. The binary can be used by itself, or as a kubectl plugin.

The snippets below install the latest version of svcat. We publish binaries for our release builds.

MacOS with Homebrew

brew update
brew install kubernetes-service-catalog-client


curl -sLO
chmod +x ./svcat
mv ./svcat /usr/local/bin/
svcat version --client


curl -sLO
chmod +x ./svcat
mv ./svcat /usr/local/bin/
svcat version --client


The PowerShell snippet below adds a directory to your PATH for the current session only. You will need to find a permanent location for it and add it to your PATH.

iwr '' -UseBasicParsing -OutFile svcat.exe
mkdir -f ~\bin
Move-Item -Path svcat.exe  -Destination ~\bin
$env:PATH += ";${pwd}\bin"
svcat version --client


  1. Download the appropriate binary for your operating system:
    • macOS:
    • Windows:
    • Linux:
  2. Make the binary executable.
  3. Move the binary to a directory on your PATH.


To use svcat as a plugin, run the following command after downloading:

$ ./svcat install plugin
Plugin has been installed to ~/.kube/plugins/svcat. Run kubectl plugin svcat --help for help using the plugin.

When operating as a plugin, the commands are the same with the addition of the global kubectl configuration flags. One exception is that boolean flags aren’t supported when running in plugin mode, so instead of using --flag you must specify a value --flag=true.

Create an Issue Edit this Page