Last active
February 25, 2019 15:47
-
-
Save jboyd01/9f5cd06e768f3b608c495438a5237dc2 to your computer and use it in GitHub Desktop.
Revisions
-
Jay Boyd revised this gist
Feb 25, 2019 . 1 changed file with 1 addition and 5 deletions.There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -25,11 +25,7 @@ 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. -
Jay Boyd renamed this gist
Feb 25, 2019 . 1 changed file with 0 additions and 0 deletions.There are no files selected for viewing
File renamed without changes. -
Jay Boyd created this gist
Feb 25, 2019 .There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -0,0 +1,35 @@ 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 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.