Accessing the web console

The OKD web console is a user interface accessible from a web browser. Developers can use the web console to visualize, browse, and manage the contents of projects.

Prerequisites

Understanding and accessing the web console

The web console runs as a pod on the master. The static assets required to run the web console are served by the pod. After OKD is successfully installed using openshift-install create cluster, find the URL for the web console and login credentials for your installed cluster in the CLI output of the installation program. For example:

Example output

  1. INFO Install complete!
  2. INFO Run 'export KUBECONFIG=<your working directory>/auth/kubeconfig' to manage the cluster with 'oc', the OpenShift CLI.
  3. INFO The cluster is ready when 'oc login -u kubeadmin -p <provided>' succeeds (wait a few minutes).
  4. INFO Access the OpenShift web-console here: https://console-openshift-console.apps.demo1.openshift4-beta-abcorp.com
  5. INFO Login to the console with user: kubeadmin, password: <provided>

Use those details to log in and access the web console.

For existing clusters that you did not install, you can use oc whoami --show-console to see the web console URL.

Multicluster console

The multicluster console provides a single interface with consistent design for the hybrid cloud console. If you enable the feature, you can switch between Advanced Cluster Management (ACM) and the cluster console in the same browser tab. It provides a simplified and consistent design that allows for shared components.

Enabling multicluster in the web console

Multicluster console is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/.

Prerequisites

Do not set this feature gate on production clusters. You will not be able to upgrade your cluster after applying the feature gate, and it cannot be undone.

Procedure

  1. Log in to the OKD web console using your credentials.

  2. Enable ACM in the administrator perspective by navigating from Administration → Cluster Settings → Configuration → Console console.operator.openshift.io → Console Plugins and click Enable for acm.

  3. A pop-up window will appear notifying you that updating the enablement of this console plugin will prompt for the console to be refreshed once it has been updated. Select Enable and click Save.

  4. Repeat the previous two steps for the mce console plugin immediately after enabling acm.

  5. A pop-up window that states that a web console update is available will appear a few moments after you enable. Click Refresh the web console in the pop-up window to update.

    You might see the pop-up window to refresh the web console twice if the second redeployment has not occurred by the time you click Refresh the web console.

    • local-cluster and All Clusters is now visible above the perspectives in the navigation section.

  6. Enable the feature gate by navigating from Administration → Cluster Settings → Configuration → FeatureGate, and edit the YAML template as follows:

    1. spec:
    2.     featureSet: TechPreviewNoUpgrade

  7. Click Save to enable the multicluster console for all clusters.

    After you save, this feature is enabled and cannot be undone.

Additional resources