Skip to content

Instantly share code, notes, and snippets.

@jboyd01

jboyd01/enablement.md

Last active February 25, 2019 15:47
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save jboyd01/9f5cd06e768f3b608c495438a5237dc2 to your computer and use it in GitHub Desktop.
Save jboyd01/9f5cd06e768f3b608c495438a5237dc2 to your computer and use it in GitHub Desktop.
Download ZIP
How to enable Service Catalog in OpenShift 4.0
Raw
enablement.md

As of Feb 24 Service Catalog is now installed by two new Cluster Operators. Initially Service Catalog is not enabled/installed. To enable it, the cluster admin must create two custom resources as follows:

cat <<EOF | oc create -f -
apiVersion: operator.openshift.io/v1
kind: ServiceCatalogAPIServer
metadata:
  name: cluster
spec:
  logLevel: "Normal"
  managementState: Managed
EOF

cat <<EOF | oc create -f -
apiVersion: operator.openshift.io/v1
kind: ServiceCatalogAPIServer
metadata:
  name: cluster
spec:
  logLevel: "Normal"
  managementState: Managed
EOF

valid values for logLevel: Normal, Debug, Trace, or TraceAll

These resources are watched by the Service Catalog operators and once the resources are created and set to a Managed state the Service Catalog API Server will be installed to the kube-service-catalog namespace and the accompanying Controller Manager will be installed to the kube-service-catalog-controller-manager namespace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment