Web console

Red Hat Advanced Cluster Management for Kubernetes 2.7

Read more to learn how to use console components.

Abstract

Read more to learn how to use console components.

Chapter 1. Web console

Learn how to access and use components of the Red Hat Advanced Cluster Management for Kubernetes console from the following documentation:

1.1. Accessing your console

The Red Hat Advanced Cluster Management for Kubernetes web console is integrated with the Red Hat OpenShift Container Platform web console as a console plug-in. You can access Red Hat Advanced Cluster Management within the OpenShift Container Platform console from the cluster switcher by selecting All Clusters. The cluster switcher is a drop-down menu that initially displays local-cluster.

Select local-cluster when you want to use OpenShift Container Platform console features on the cluster where you installed Red Hat Advanced Cluster Management. Select All Clusters when you want to use Red Hat Advanced Cluster Management features to manage your fleet of clusters.

If the cluster switcher is not present, the required console plug-ins might not be enabled. For new installations, the console plug-ins are enabled by default. If you upgraded from a previous version of Red Hat Advanced Cluster Management and want to enable the plug-ins, or if you want to disable the plug-ins, complete the following steps:

  1. To disable the plug-in, be sure you are in the Administrator perspective in the OpenShift Container Platform console.
  2. Find Administration in the navigation and click Cluster Settings, then click the Configuration tab.
  3. From the list of Configuration resources, click the Console resource with the operator.openshift.io API group, which contains cluster-wide configuration for the web console.
  4. Select the Console plug-ins tab. Both the acm and mce plug-ins are listed.
  5. Modify plug-in status from the table. In a few moments, you are prompted to refresh the console.

Note: If you are using OpenShift Container Platform 4.12, you can enable and disable the console. See MultiClusterHub advanced for information.

To learn more about the Red Hat Advanced Cluster Management for Kubernetes console, see Console overview.

1.2. Console overview

Learn more about console components that you can use to view, manage, or customize your console.

See the following image of the Navigation from the Red Hat Advanced Cluster Management for Kubernetes console, which is described in more detail later in each section. See that the navigation represents major production function.

Navigation

1.2.1. Console components

1.2.2. Home

From the Red Hat Advanced Cluster Management for Kubernetes Home page, you get more information about the product and you can access header features, as well as the pages for the major components of the product.

  • Access the Welcome page and the Overview, which gives you visibility into your clusters.

    You can view the following information about your clusters on the Overview dashboard:

    • Metric data from your managed clusters by selecting the Grafana link
    • Cluster and node counts across all clusters and for each provider
    • Cluster status
    • Cluster compliance
    • Pod status
  • Select Grafana to access the Grafana dashboard.
  • Click Add provider connections to access the Clusters page.

Search is also available from the Home tab. To learn about Search, see Searching in the console introduction.

1.2.3. Infrastructure

From Clusters, you can create new clusters or import existing clusters. From Automation, you can create an Ansible template.

For more information about managing clusters, see The multicluster engine operator cluster lifecycle overview.

Additionally, see specific information on these cluster types at Configuring Ansible Automation Platform tasks to run on managed clusters.

1.2.4. Applications

Create an application and edit a .yaml file. Access an overview or more advanced information about each application. For more information about application resources, see Managing applications.

1.2.5. Governance

Create and edit a .yaml file to create a policy. Use the Governance dashboard to manage policies and policy controllers.

For more information, see Governance.

1.2.6. Credentials

The credential stores the access information for a cloud provider. Each provider account requires its own credential, as does each domain on a single provider.

Review your credentials or add a credential.

See Managing credentials overview for more specific information about providers and credentials.

Legal Notice

Copyright © 2024 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.