Chapter 2. Using the Red Hat Lightspeed advisor service


The Red Hat Lightspeed advisor service repeatedly analyzes the data collected by the Insights Operator. You can view and manage reports showing advisor results for your OpenShift cluster in the advisor service GUI on the Red Hat Hybrid Cloud Console.

2.1. Displaying potential issues with your cluster

This section describes how to view advisor results in the Red Hat Lightspeed GUI.

Note that the Insights Operator repeatedly analyzes your cluster and shows the latest results in the Red Hat Lightspeed advisor service. These results can change if you fix an issue or a new issue has been detected, for example.

Prerequisites

  • Your cluster is registered with Red Hat OpenShift Cluster Manager.
  • Remote health reporting is enabled, which is the default.
  • You are logged in to the Hybrid Cloud Console.

Procedure

  1. Navigate to Operations > Advisor > Recommendations.

    Depending on the result, you may see one of the following messages:

    • No matching recommendations found, if Red Hat Lightspeed did not identify any issues.
    • A list of issues Red Hat Lightspeed has detected, grouped by risk (low, moderate, important, and critical).
    • No clusters yet, if Red Hat Lightspeed has not yet analyzed the cluster. The analysis starts shortly after the cluster has been installed, registered, and connected to the internet.
  2. If any issues are displayed, click the > icon in front of the entry for more details.

    Depending on the issue, the details can also contain a link to more information from Red Hat about the issue.

The Recommendations view, by default, only displays the recommendations that are detected on your clusters. However, you can view all of the recommendations contained in the Red Hat Lightspeed archive.

Prerequisites

  • Remote health reporting is enabled, which is the default.
  • Your cluster is registered with Red Hat OpenShift Cluster Manager.
  • You are logged in to the Hybrid Cloud Console.

Procedure

  1. Navigate to Operations > Advisor > Recommendations.
  2. Click the X icons next to the Clusters Impacted and Status filters.

    You can now browse through all of the recommendations against which your cluster is scanned.

The Red Hat Lightspeed advisor service can return a large number of recommendations. To focus on your most critical recommendations, you can apply filters to the advisor service recommendations list to remove low-priority recommendations.

By default, filters are set to only show enabled recommendations that are impacting one or more clusters. To view all or disabled recommendations in the Red Hat Lightspeed library, you can customize the filters.

To apply a filter, select a filter type and then set its value based on the options that are available in the drop-down list. You can apply multiple filters to the list of recommendations.

You can set the following filter types:

  • Name: Search for a recommendation by name.
  • Total risk: Select one or more values from Critical, Important, Moderate, and Low indicating the likelihood and the severity of a negative impact on a cluster.
  • Impact: Select one or more values from Critical, High, Medium, and Low indicating the potential impact to the continuity of cluster operations.
  • Likelihood: Select one or more values from Critical, High, Medium, and Low indicating the potential for a negative impact to a cluster if the recommendation comes to fruition.
  • Category: Select one or more categories from Service Availability, Performance, Fault Tolerance, Security, and Best Practice to focus your attention on.
  • Status: Click a radio button to show enabled recommendations (default), disabled recommendations, or all recommendations.
  • Clusters impacted: Set the filter to show recommendations currently impacting one or more clusters, non-impacting recommendations, or all recommendations.
  • Risk of change: Select one or more values from High, Moderate, Low, and Very low indicating the risk that the implementation of the resolution could have on cluster operations.

As an OpenShift Container Platform cluster administrator, you can filter the advisor recommendations that are displayed on the recommendations list. By applying filters, you can reduce the number of reported recommendations and concentrate on your highest priority recommendations.

The following procedure demonstrates how to set and remove Category filters; however, the procedure is applicable to any of the filter types and respective values.

Prerequisites

You are logged in to the Hybrid Cloud Console.

Procedure

  1. Navigate to Operations > Advisor > Recommendations.
  2. In the main, filter-type drop-down list, select the Category filter type.
  3. Expand the filter-value drop-down list and select the checkbox next to each category of recommendation you want to view. Leave the checkboxes for unnecessary categories clear.
  4. Optional: Apply additional filters to further refine the list.

Only recommendations from the selected categories are shown in the list.

Verification

  • After applying filters, you can view the updated recommendations list. The applied filters are added next to the default filters.

You can apply multiple filters to the list of recommendations. When ready, you can remove them individually or completely reset them.

Removing filters individually

  • Click the X icon next to each filter, including the default filters, to remove them individually.

Removing all non-default filters

  • Click Reset filters to remove only the filters that you applied, leaving the default filters in place.

2.4. Disabling advisor recommendations

You can disable specific recommendations that affect your clusters, so that they no longer appear in your reports. It is possible to disable a recommendation for a single cluster or all of your clusters.

Note

Disabling a recommendation for all of your current clusters also disables that recommendation on all future clusters.

Prerequisites

  • Remote health reporting is enabled, which is the default.
  • Your cluster is registered with Red Hat OpenShift Cluster Manager.
  • You are logged in to the Red Hat Hybrid Cloud Console.

Procedure

  1. Navigate to Operations > Advisor > Recommendations.
  2. Disable the recommendation for a single cluster:

    1. Click the name of the recommendation to disable. You are directed to the details page for the recommendation.
    2. Click the options icon (⋮) for that cluster, and then click Disable recommendation for cluster.
    3. Enter a justification note and click Save.
  3. Disable the recommendation for all of your clusters:

    1. Click the name of the recommendation to disable. You are directed to the details page for the recommendation.
    2. Click Actions > Disable recommendation.
    3. Enter a justification note and click Save.

Verification

  1. If you disabled the recommendation for all clusters, go to Operations > Advisor > Recommendations and search for the recommendation. If the procedure was successful, you will not see the recommendation in the search result.
  2. If you disabled the recommendation for an individual cluster, go to the Recommendations page and search for the recommendation.
  3. Click on the recommendation and search for the cluster ID for the cluster on which it was disabled. If the procedure was successful, you will not see your cluster in the list of clusters affected by the recommendation.

When a Red Hat Lightspeed advisor recommendation is disabled for all clusters, you will no longer see it on the list of recommendations. You can reenable the recommendation so that your clusters are scanned for it.

Prerequisites

  • Remote health reporting is enabled, which is the default.
  • Your cluster is registered with Red Hat OpenShift Cluster Manager.
  • You are logged in to the Red Hat Hybrid Cloud Console.

Procedure

  1. Navigate to Operations > Advisor > Recommendations.
  2. Filter the recommendations by Status > Disabled.
  3. Locate the recommendation to enable.
  4. Click the options icon (⋮), and then click Enable recommendation.

Red Hat Lightspeed repeatedly analyzes your cluster and you can display the status of identified potential issues of your cluster in the Red Hat OpenShift Container Platform web console. This status shows the number of issues in the different categories and, for further details, links to the reports in the Red Hat Hybrid Cloud Console.

Prerequisites

  • Your cluster is registered with Red Hat OpenShift Cluster Manager.
  • Remote health reporting is enabled, which is the default.
  • You are logged in to the OpenShift Container Platform web console.

Procedure

  1. Navigate to Home Overview in the OpenShift Container Platform web console.
  2. Click Red Hat Lightspeed on the Status card.

    The pop-up window lists potential issues grouped by risk. Click the individual categories or View all recommendations in Red Hat Lightspeed ADVISOR to display more details.

Update-risk assessment uses machine learning developed in collaboration with IBM Research to compare the recent state of the cluster with conditions known to cause updates to fail, including failing operator conditions, alerts, and other metrics.

The advisor service identifies clusters with update risks, and also shows you alerts and components that need attention. You can use the update-risk feature to generate a checklist of issues to fix before beginning a cluster update.

Complete the following steps to view any update risks in your clusters.

Prerequisites

  • Cluster is connected to the Red Hat Hybrid Cloud Console by using the instructions in the Enabling remote health reporting chapter of the Red Hat OpenShift Container Platform documentation.
  • Cluster has sent data to Red Hat within the last two hours.
  • You are logged into the Red Hat Hybrid Cloud Console.

Procedure

  1. Navigate to the Advisor clusters page in the Hybrid Cloud Console.
  2. Select a cluster with the Update risk label. The label is visible with the cluster name or ID.

    Cluster name with the update-risk label

  3. Click the cluster name to open the cluster details page.

    • If no risks exist for the cluster, a banner displays the message, "No known update risks identified for this cluster."
    • If the cluster has not checked in for more than two hours, the banner message says "Warning alert: Update risks are not currently available. This cluster has gone more than two hours without sending metrics. Check the cluster’s web console if you think that this is incorrect."
  4. Click the Update risks tab.

    The Update risks tab showing risks

  5. View alerts or cluster operator risks for the cluster.
  6. Click an alert to open the Alert details page in the OpenShift Container Platform web console.
  7. Click a cluster operator to open the in-cluster, ClusterOperator details page in the OpenShift Container Platform web console.

For more information about alerts, see the following Red Hat OpenShift Container Platformdocumentation: * Getting information about alerts, silences, and alerting rules.

The Red Hat Lightspeed advisor service compiles workload recommendations for specific objects in namespaces in clusters and outputs them to OpenShift > Advisor > Workloads. Workload recommendations are best practices for cloud-native Kubernetes applications and highlight misconfigurations within specific namespaces in managed and on-premise clusters in your organization.

Workload recommendations are based on data provided by the Deployment Validation Operator (DVO), which executes KubeLinter checks.

If you are a cluster administrator, you can view workload recommendation details, including cluster, namespace, and affected object IDs, and also steps to resolve the issue in OpenShift > Advisor > Workloads. As a cluster administrator, you can also either fix the issue or inform developers who manage the namespaces so that they can apply a resolution.

You can view and gather information about recommendations for specific objects in namespaces in your clusters by viewing them in the Workloads view of the Red Hat Hybrid Cloud Console. Depending on whether you have a managed or self-managed cluster, you will see the following:

  • For self-managed clusters: cluster name and namespace name
  • For managed clusters: cluster name and namespace UUID

Prerequisites

  • You have access as a cluster administrator to at least one cluster in your infrastructure.
  • You have logged in to the Red Hat Hybrid Cloud Console.

Procedure

  1. Go to OpenShift > Advisor > Workloads.
  2. Click a namespace (identified by cluster and namespace) to display the namespace details page, which includes recommendations based on the Deployment Validation Operator (DVO) checks for this namespace.

    Note

    You can use the filtering function to search by cluster name or namespace name.

  3. Click the arrow next to a recommendation to see the following information about the issue:

    • A description of the detected issue
    • Steps to resolve the issue on affected objects in the namespace
    • Identifiers for affected objects in the namespace
    • Additional resources and information
  4. Click View all objects to view a list of all of the objects affected by the recommendation in this namespace.

You can use this information to work with your developers to resolve issues, as needed. In some cases, you might find that your organization’s policies are different from a recommendation and the proposed solution to resolve it. In these cases, you can exclude objects from workload recommendations.

After viewing workload recommendations, you might decide that some of the recommendations for specific objects in a cluster are not aligned with your organization’s policies or cluster management workflow. You can exclude these recommendations from view by excluding specific objects from the Deployment Validation Operator (DVO) checks. For example, you might have a cluster recommendation to run as non-root, because your organization has some containers running as root. You can change your configuration to turn off the recommendation and exclude the specified workload object from future Deployment Validation Operator (DVO) checks.

Prerequisites

  • You have OCP Advisor administrator permissions to a cluster.
  • You have permission to edit the namespace.
  • You have logged in to the Red Hat Hybrid Cloud Console.
  • You have identified a cluster with a recommendation and have at least one object in Workloads that you want to exclude.

Procedure

  1. Navigate to OpenShift > Advisor > Workloads.
  2. Click a namespace that relates to the recommendation that includes the object you want to exclude. A namespace is identified by cluster and namespace.

    Note

    You can use the filtering function to search by the following:

    • For self-managed clusters: cluster name and namespace name
    • For managed clusters: cluster name and namespace UUID
  3. Expand Description on the details page to see all issues or click the arrow next to a recommendation to see the following information about the issue:

    • A description of the detected issue
    • Steps to resolve the issue on affected objects in the namespace
    • Identifiers for affected objects in the namespace
    • Additional resources and information
  4. Note the name of the KubeLinter check, for example run-as-non-root or non-isolated-pod.
  5. In the Steps to resolve section, click View all objects to display a list of all of the objects affected by the recommendation in this namespace.
  6. Note the Name and Kind values for the workload object you want to exclude from the Deployment Validation Operator’s (DVO) KubeLinter checks. You will need this information to change the annotation for the object.
  7. Use Ignoring specific resources in the Github resource for Deployment Validation Operator (DVO) to annotate the object based on your organization’s workflow. The following example shows a change to the annotation in the nginx deployment object in the project named test-dvo to exclude the nginx object from the KubeLinter check run-as-root. In this YAML example, you would add the annotation, ignore-check.kube-linter.io/run-as-non-root: "This image must be run as a privileged user for it to work..

    kind: Deployment
    apiVersion: apps/v1
    metadata:
      annotations:
        deployment.kubernetes.io/revision: '1'
        kubectl.kubernetes.io/last-applied-configuration: |
          {"apiVersion":"apps/v1","kind":"Deployment","metadata":{"annotations":{},"labels":{"app":"nginx"},"name":"nginx","namespace":"test-dvo"},"spec":{"replicas":3,"selector":{"matchLabels":{"app":"nginx"}},"template":{"metadata":{"labels":{"app":"nginx"}},"spec":{"containers":[{"image":"nginxinc/nginx-unprivileged:1.18","name":"nginx","ports":[{"containerPort":8080}]}]}}}}
        ignore-check.kube-linter.io/run-as-non-root: "This image must be run as a privileged user for it to work.”
      resourceVersion: '114842'
      name: nginx
      uid: bf934080-0e21-4ae3-a6d1-d6d077b8d6f3
    Copy to Clipboard Toggle word wrap
  8. It takes approximately two hours for the Insights Operator to update the recommendations. After the update completes, the recommendation for the specific object is no longer shown in the annotation.

Verification step

Wait approximately two hours or until the Insights Operator has updated the recommendations, and then log on as a cluster administrator and check that the object is excluded from the workload recommendation.

The Deployment Validation Operator validates on-premise and managed clusters against a curated collection of KubeLinter checks. These checks implement best practices for Kubernetes-native workloads, helping to ensure that applications are optimized for the operational stability of the cluster.

The Insights Operator gathers Deployment Validation Operator checks every two hours by default and presents data in the Red Hat Lightspeed advisor service. If the Deployment Validation Operator detects issues, cluster administrators can view resolutions in the advisor service. If the Deployment Validation Operator detects no issues, no results are visible in the advisor service.

Curated KubeLinter checks

The Deployment Validation Operator checks a curated, limited collection of all of the available KubeLinter checks. The Deployment Validation Operator does not execute the whole list of available KubeLinter checks. Red Hat Lightspeed advisor service recommendations do not exist for all available KubeLinter checks.

Supported Red Hat OpenShift Container Platform versions

All Red Hat-supported versions of Red Hat OpenShift Container Platform, Red Hat OpenShift Dedicated, and Red Hat OpenShift Service on AWS support the Deployment Validation Operator.

Important

With a managed OpenShift Container Platform cluster, the Deployment Validation Operator is installed and operational by default. For an on-premise OpenShift Container Platform cluster, a cluster administrator must download and install the Deployment Validation Operator from OperatorHub and can change the default list of checks.

The Deployment Validation Operator is already installed and operational on managed OpenShift Container Platform clusters. This includes clusters on Red Hat OpenShift Dedicated and Red Hat OpenShift Service on AWS.

Deployment Validation Operator configuration

The Deployment Validation Operator for managed clusters comes preconfigured, by default. The Deployment Validation Operator configuration file contains the default, curated set of KubeLinter checks and is not editable.

Deployment Validation Operator updates

On managed clusters, the Deployment Validation Operator updates automatically.

Administrators of on-premise clusters must install the Deployment Validation Operator from OperatorHub in the OpenShift Container Platform web console. On-premise cluster administrators can also configure the default set of KubeLinter checks.

Note

The advisor does not have recommendations for all of the checks that KubeLinter has available.

You can find the Deployment Validation Operator in OperatorHub and install it from there.

Prerequisites

  • You are logged into the Red Hat OpenShift Container Platform web console as a cluster-admin.

Procedure

  1. Navigate to Red Hat OpenShift Container Platform web console > Operators > OperatorHub.
  2. In the Search box, start typing “deployment-validation-operator."
  3. Click on the DVO card when you see it.
  4. The Deployment Validation Operator card displays information about capabilities, configuration, version, and GitHub source files. When you are ready to install the Operator, click Install.
  5. Choose the namespace or use the default.
  6. Click Install and the Operator installs. You can confirm the installation in the InstalledOperators view. The Deployment Validation Operator is also visible in the Pods and Deployments views for the cluster in the corresponding namespace.

If you are an administrator of an on-premise OpenShift Container Platform cluster, you can change the default list of Deployment Validation Operator checks to focus on specific best practices of interest. For more information, see Configuring Checks, in the Deployment Validation Operator GitHub repository.

You can set the Deployment Validation Operator to automatically update during the installation from OperatorHub.

If the Deployment Validation Operator detects issues, the Overview page for the cluster in the OpenShift Container Platform web console shows a Red Hat Lightspeed link with the number of detected issues in the Status information block. Click the link to learn more about the issue and how to resolve it in the advisor service in the Red Hat Hybrid Cloud Console.

Note

If the latest Deployment Validation Operator returns no issues, you will not see any issues in Red Hat Lightspeed.

Prerequisites

  • You are logged into the Red Hat Hybrid Cloud Console.

Procedure

  1. Go to the Overview page for the cluster in the OpenShift Container Platform web console.
  2. Look for the Status block, a Red Hat Lightspeed link, and the number of detected issues.
  3. If one or more issues exist, click the Red Hat Lightspeed link to open the advisor service in the Hybrid Cloud Console.

    The cluster information page displays. On the Recommendations tab, you can see the issues detected for the cluster.

  4. Click the arrow to view complete information about the issue, including the necessary actions to resolve it.

The Deployment Validation Operator checks your cluster against a default list of checks. You can view the list of DVO checks in GitHub.

Important

Administrators of managed clusters cannot modify the list of default checks, but can view them using the link above.

Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat