vRealize Operations Management Pack for Kubernetes | 10 JUN 2021 | Build 18053243

What's in the Release Notes

The release notes cover the following topics:

Introduction

The VMware vRealize Operations Management Pack for Kubernetes delivers self-driving IT operations management for private, hybrid, and multi-cloud environments in a unified, AI-powered platform. vRealize Operations Manager can monitor multiple Kubernetes solutions, whether it is VMware Tanzu Kubernetes Grid Integrated (TKGI), RedHat OpenShift, or Kubernetes on Amazon Web Services EC2, Azure, or Google Virtual Machines.

What's New

  • The VMware vRealize Operations Management Pack for Kubernetes 1.5.2 supports the following integrations:
    • Upstream Kubernetes 1.16–1.20
    • Tanzu Kubernetes Grid Integrated or Tanzu Kubernetes Grid 1.6–1.11
    • OpenShift 4.2–4.7
  • Tanzu Mission Control (TMC) Support
    • Automated Guest Cluster Discovery & Removal for TMC provisioned Tanzu Kubernetes clusters on Amazon Web Services.

Compatibility

For compatibility between products, please refer to the VMware Product Interoperability Matrices.

Limitations

  • Autodiscovery is supported only for VMware Tanzu Mission Control (TMC) clusters provisioned on Amazon Web Services and Tanzu Kubernetes Grid Integrated.
  • Autodeletion of Kubernetes clusters is not supported for adapter instance which is not in collection state.
  • The management pack supports metrics collection only in docker runtime.
  • Discovery of the Replication Controller has been disabled.
  • API versions are limited to:
    • extensions/v1beta1 on Kubernetes v1.5.x – 1.7.x
    • apps/v1beta2 on Kubernetes v1.8.x
    • apps/v1 on Kubernetes 1.9.x and above
  • The following authentication providers are supported in vRealize Operations Management Pack for Container Monitoring.
    • Internal UAA
    • LDAP Server

General Information

  • For a Pod object to collect metrics, enable Super Metric Memory Usage(MB) and CPU Usage (Cores). To enable super metric, perform the following:
    • Click Administration.
    • In the left pane click Configuration > Super Metrics.
    • Select active policy from the Policy library and click Edit.
    • Select the Collect metrics and properties tab.
    • Set Attribute Type to Super Metric and Object type to Kubernetes pod and enable the Memory Usage (MB) and CPU Usage (Cores) metrics.
  • The Disk IO metric for node might be missing in some clusters due to the variations in Kubelet configuration.
  • The VMware TKGI adapter instance auto-discovers the Kubernetes clusters available in the VMware TKGI Environment. It creates an appropriate Kubernetes Cluster Resource and a Kubernetes adapter instance against each cluster.
  • The VMware TMC adapter instance auto-discovers the Kubernetes clusters available in the VMware TMC Environment. It creates an appropriate Kubernetes Cluster Resource and a Kubernetes adapter instance against each cluster.
  • Metrics of Container Object might be missing in some clusters if the cAdvisor Daemonset is not configured or if the port is not reachable.

Known Issues

  • Some Prometheus exporter metrics are propagated to parent objects as the PromQL matches the same metric.

    Some Prometheus exporter metrics are propagated to parent objects as the PromQL matches the same metric. So, the the same set of metrics are grouped under parent Kubernetes objects. For example: The Container metrics are grouped under Pod/Node/Namespace.

    Workaround: None

  • If you upgrade from VMware vRealize® Operations Management Pack™ for Container Monitoring 1.0 to 1.2.1, the collection state displays a status called Not Collecting for all the adapter instances.

    This occurs because of the addition of new settings and credential types in the 1.1 version of VMware vRealize® Operations Management Pack™ for Container Monitoring.

    Note: If you upgrade from VMware vRealize Operations Management Pack for Container Monitoring 1.1 to 1.2.1, you do not have to complete the steps listed below.

    Workaround: All the adapter instances must be deleted and recreated. This will lead to creation of new objects. However, you can retain the old objects to keep historical data intact.

    1. From the main menu of vRealize Operations Manager, click Administration, and then in the left pane click Solutions.
    2. From the Solutions page, select VMware vRealize Operations Management Pack for Container Monitoring.
    3. Click the Configure icon. The Manage Solution dialog box appears.
      • Select an adapter instance.
      • Click the Delete icon.
      • When the Confirmation dialog box appears and if you want to retain historical data, deselect the option Remove related objects.
    4. Recreate the adapter instance by following steps provided in User Guide.
    5. Repeat the above steps for all adapter instances.
  • During configuration, VMware vRealize® Operations Management Pack™ for Container Monitoring verifies if the cAdvisor service is accessible on every node. An error message similar to the following may appear: Unable to establish a valid connection to the target system. cAdvisor service on following nodes is either not reachable OR of a lower version than v2.1.

    The error occurs if the cAdvisor service is inaccessible or if the API version is lesser than 2.1. You may sometimes receive this error if the cAdvisor service temporarily throws a gateway error at the time of verification.

    Workaround:

    1. Verify if the cAdvisor service is up and running on the affected nodes and responds to API calls.
    2. Verify if the API version of the cAdvisor service is later than 2.1. If not, deploy the latest version of the cAdvisor service.

    If you have completed the above two steps, you can ignore the error message and continue to save the adapter instance.

  • Under recommendations, the Defined by column is displayed as KubernetesAdapter3.

    Under recommendations, the Defined by column is displayed as KubernetesAdapter3.

  • Deleting the VMware PKS adapter instance does not remove the Kubernetes adapter instances created by the VMware PKS adapter instance

    When you delete the VMware PKS adapter instance, the Kubernetes adapter instances created by the VMware PKS adapter instance will not be removed.

    Workaround : Manually delete the adapter instances related to the VMware PKS adapter instance

  • The Environment Overview dashboard does not display the relationship between the vCenter Hosts/Virtual Machines and the Kubernetes nodes

    If the vRealize Operations Manager accesses the K8s through proxy, the vCenter adapter instance does not provide a provision to specify proxy. So, the Environment Overview dashboard may not display the relationship between the vCenter Hosts/Virtual Machines and the Kubernetes nodes.

    Workaround: None

  • Data collection fails for the K8s adapters that are auto-configured by the VMware PKS adapter

    The auto-configured K8s adapter instances that presents the untrusted SSL certificates will have the collection status as 'Failed'.

    Workaround: Manually accept the untrusted certificate for the auto-configured K8s adapter instances for which data collection has failed

  • Adding the VMware PKS adapter will configure the K8s instances but does not create the vCenter adapter instances

    Adding the VMware PKS adapter will configure the K8s instances but does not create the vCenter adapter instances or associate it with the vCenters that the Kubernetes cluster nodes are deployed in.


    Workaround: Manually configure the vCenter adapter instances and then add the details to the K8s adapters that are auto-configured by VMware PKS

  • Expired certificates are also auto accepted when the 'Auto-accept Kubernetes Cluster SSL Certificate' option is enabled

    When you enable the 'Auto-accept Kubernetes Cluster SSL Certificate' under Advanced Settings, the expired certificates are also auto accepted and there is no prompt.

    Workaround: None

  • Container File System base usage (MB) should be referred as file system base limit

    The Container File System base usage (MB) should be referred as file system base limit. This is applicable only for Prometheus monitored containers.

    Workaround: None

  • DiskIO|Sync and DiskIO|Async Container metrics will not be shown in vRealize Operations Manager 

    The DiskIO|Sync and DiskIO|Async Container metrics will not be shown in vRealize Operations Manager for Prometheus monitored containers. 

    Workaround: None

check-circle-line exclamation-circle-line close-line
Scroll to top icon