doc cluster up --service-catalog flag
- [Persistent Volumes](#persistent-volumes)
- [Using a Proxy](#using-a-proxy)
- [Installing Metrics](#installing-metrics)
-- [Intalling Logging Aggregation](#installing-logging-aggregation)
+- [Installing Logging Aggregation](#installing-logging-aggregation)
+- [Installing the Service Catalog](#installing-the-service-catalog)
- [Administrator Access](#administrator-access)
- [Docker Machine](#docker-machine)
- [Configuration](#configuration)
@@ -304,7 +305,7 @@ Cluster up will warn you if there is a discrepancy between the Docker settings a
## Installing Metrics
-You can install metrics components by specifying the --metrics argument when invoking `oc cluster up`.
+You can install metrics components by specifying the `--metrics` argument when invoking `oc cluster up`.
To see metrics in the web console, you must first browse to the Hawkular metrics UI URL displayed when `cluster up` starts.
@@ -315,11 +316,34 @@ To see metrics in the web console, you must first browse to the Hawkular metrics
| ---- |
| This feature requires an oc command v1.4 or newer |
-You can install logging aggregation components by specifying the --logging argument when invoking `oc cluster up`.
+You can install logging aggregation components by specifying the `--logging` argument when invoking `oc cluster up`.
With logging aggregation installed, a new link will appear in the logs tab of a running pod in the web console.
+## Installing the Service Catalog
+
+| NOTE |
+| ---- |
+| This feature requires an oc command v3.6 or newer. |
+| Enabling this feature renders the entire cluster "Tech Preview". |
+
+
+You can enable the service catalog component by specifying the `--service-catalog` argument when invoking `oc cluster up`.
+
+Enabling the service catalog has the following effect:
+
+1. The API aggregator is enabled to provide a unified API endpoint for both OpenShift/Kubernetes resources and the new APIs introduced by the service catalog.
+1. A service catalog deployment is created to deploy and run the service catalog.
+1. The template broker is enabled in the OpenShift master server and registered with the service catalog.
+1. The web console is configured to use the new service catalog landing page.
+
+On completion, `oc cluster up` will output a command that you may run if you want to use the template broker with the service catalog. CAUTION: running this command has significant adverse security effects as it enables unauthenticated access to the template broker. This allows anyone who can access your master to provision templates into any project as any user.
+
+The service catalog can be used without the template broker, however no other brokers are provided out of the box with `oc cluster up` (though they can be registered with the service catalog manually).
+
+
+
## Administrator Access
To login as administrator to your cluster, login as `system:admin`:
