Accessing the Mission Control console

DataStax services that are created in watsonx.data console can be managed through the Mission Control console.

Prerequisite

To enable access to the Mission Control console, an OpenShift user who is managing the operators namespace must expose the Mission Control UI outside the cluster.

  1. Collect the default dex admin credentials (username and password) that were generated during the installation from the operator namespace.
oc extract secret/datastax-mc-embedded-ui-dex-admin-credentials -n $PROJECT_CPD_INST_OPERATORS --to=-
  1. Create an OpenShift route to make the Mission Control UI accessible.
cat <<EOF | oc apply --namespace $PROJECT_CPD_INST_OPERATORS -f -
apiVersion: route.openshift.io/v1
kind: Route
metadata:
  name: datastax-mc-ui
spec:
  tls:
    termination: passthrough
  to:
    kind: Service
    name: datastax-mc-ui
    weight: 100
EOF
  1. Label and annotate the namespaces to enable Mission Control UI to monitor them.
oc label ns $INSTANCE_NS mission-control.datastax.com/is-project=true
oc annotate ns $INSTANCE_NS mission-control.datastax.com/project-name=$INSTANCE_NS

Procedure

To access the Mission Control console, complete the following steps:

  1. Log in to the watsonx.data console.

  2. From the navigation menu, select Infrastructure Manager.

  3. Select the IBM DataStax service that is in Running state.

  4. Click the Mission Control route to open the console.

  5. Use the default email admin@local along with the password obtained earlier from the dex credentials to log in to the Mission Control console.