Chapter 3. Installing while connected online

To ensure that the OpenShift Container Platform cluster is set up correctly, access the OpenShift Container Platform web console with the following command:

kubectl -n openshift-console get route

See the following example output:

openshift-console console console-openshift-console.apps.new-coral.purple-chesterfield.com
console   https   reencrypt/Redirect     None

On the Operator Installation page, select the options for your installation:

Note: To upgrade to the next minor release, you must return to the OperatorHub page and select a new channel for the more current release.

See the following process to create the MultiClusterEngine custom resource.

Select Create to initialize the custom resource. It can take up to 10 minutes for the multicluster engine for Kubernetes engine to build and start.

After the MultiClusterEngine resource is created, the status for the resource is Available on the MultiCluster Engine tab.

Create a multicluster engine for Kubernetes engine namespace where the operator requirements are contained. Run the following command, where namespace is the name for your multicluster engine for Kubernetes engine namespace. The value for namespace might be referred to as Project in the OpenShift Container Platform environment:

oc create namespace <namespace>

Switch your project namespace to the one that you created. Replace namespace with the name of the multicluster engine for Kubernetes engine namespace that you created in step 1.

oc project <namespace>

Create a YAML file to configure an OperatorGroup resource. Each namespace can have only one operator group. Replace default with the name of your operator group. Replace namespace with the name of your project namespace. See the following example:

apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
  name: <default>
spec:
  targetNamespaces:
  - <namespace>

Run the following command to create the OperatorGroup resource. Replace operator-group with the name of the operator group YAML file that you created:

oc apply -f <path-to-file>/<operator-group>.yaml

Create a YAML file to configure an OpenShift Container Platform Subscription. Your file should look similar to the following example:

apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: multicluster-engine
spec:
  sourceNamespace: openshift-marketplace
  source: redhat-operators
  channel: stable-1.0
  installPlanApproval: Automatic
  name: multicluster-engine

Note: For installing the multicluster engine for Kubernetes engine on infrastructure nodes, the see Operator Lifecycle Manager Subscription additional configuration section.

Run the following command to create the OpenShift Container Platform Subscription. Replace subscription with the name of the subscription file that you created:

oc apply -f <path-to-file>/<subscription>.yaml

Create a YAML file to configure the MultiClusterEngine custom resource. Your default template should look similar to the following example:

apiVersion: multicluster.openshift.io/v1
kind: MultiClusterEngine
metadata:
  name: multiclusterengine
spec: {}

Note: For installing the multicluster engine for Kubernetes engine on infrastructure nodes, see the MultiClusterEngine custom resource additional configuration section:

Run the following command to create the MultiClusterEngine custom resource. Replace custom-resource with the name of your custom resource file:

oc apply -f <path-to-file>/<custom-resource>.yaml

If this step fails with the following error, the resources are still being created and applied. Run the command again in a few minutes when the resources are created:

error: unable to recognize "./mce.yaml": no matches for kind "MultiClusterEngine" in version "operator.multicluster-engine.io/v1"

Run the following command to get the custom resource. It can take up to 10 minutes for the MultiClusterEngine custom resource status to display as Available in the status.phase field after you run the following command:

oc get mce -o=jsonpath='{.items[0].status.phase}'