Skip to content

Managed Add-Ons

Managed System Add-ons are available in the controller by default for the users and one or more managed add-ons can be added to a blueprint to deploy on the cluster

  • Managed Storage
  • Ingress Controller
  • Log Aggregation
  • Monitoring & Alerting
  • VM Operator
  • K8s Management operator
  • CSI Driver

Managed System Add-Ons

Managed Storage (Optional)

Managed Storage enables the Ceph/Rook storage addon, which can be deployed to your cluster(s) during provision to avail distributed storage systems. On selecting the check box, a wrench settings icon appears. Click on the icon to view the enablement of Rook Ceph Storage

Ingress Controller (Optional)

Ingress controller, selected by default in the Controller, is a specialized load balancer for Kubernetes (and other containerized) environments. This specific add-on accepts traffic from outside the Kubernetes platform and load balance it to pods (containers) running inside the platform. It monitors the pods running in Kubernetes and automatically update the load‑balancing rules when pods are added or removed from a service

Log Aggregation (Optional)

Log Aggregation, selected by default, collects real-time log data from the applications, and servers. This specific add-on helps to analyze and troubleshoot incidents, identify trends and set alerts, create comprehensive per-user access control policies, and automated backups

Monitoring & Alerting (Optional)

Monitoring & Alerting, selected by default, collects the various metrics from different system services and generates alerts. This specific add-on helps to record real-time metrics in a time series database (allowing for high dimensionality), with real-time alerting. Users are allowed to customize the Monitoring & Alerting add-on. Click the Wrench icon of the Monitoring & Alerts and the Customize Prometheus Addons pane appears to the right

Customize Prometheus Add-Ons

Enabling Monitoring & Alerting Add-ons helps to update the controller dashboards of various metrics associated with clusters

  • Kube State Metrics: Exposes Prometheus format metrics based on the current state of the Kubernetes resources and this component is selected by default. Users who wish to provide their own Kube State Metrics, perform the below steps:

    • Disable the Kube State Metrics component
    • Provide the Kubernetes Namespace where the Kube State Metrics has been deployed in the cluster
    • Select the resource to discover Service or Pod
    • Click Add Key-Value Labels to add one or more labels if required

These information are collected and forwarded to the Time Series Database. Time Series Database (TSDB) is specifically for handling metrics and events or measurements that are time-stamped and these data change over time

  • Node Exporter: Exposes Prometheus format metrics based on the current state of the Kubernetes nodes and this metric is selected by default. A Prometheus Node Exporter fetch statistics from an application, converts those statistics into metrics, and expose them to the controller. Similar to Kube State Metrics, users can disable this option and provide their own Node Exporter metrics

  • Helm Exporter: Exposes helm release, chart, and version statistics in the controller. Users who wish to provide their own Helm metrics can disable this option and provide their Helm metrics

Note: Kube State Metrics, Node Exporter, and Helm Exporter plays a major role in exposing the metrics in the controller dashboard. Invalid data might break the dashboard

  • Prometheus Adapter: Prometheus Adapter is used for HPA (Horizontal Pod Autoscaler). Enabling this metric to use for automatically scaling workload up or down based on resource usage. In Kubernetes, the Horizontal Pod Autoscaler (HPA) can scale pods based on observed CPU utilization and memory usage

  • Metrics Server: Metrics Server provides metrics for resource utilization like CPU & Memory. This metric discovers all the nodes in the cluster and forwards the details for resource utilization


Disable Prometheus Adapter and Metrics Server to deploy AKS clusters

  • Resources Limits (Optional): Specify the number of resources a Container needs. Users can set the CPU and Memory Limits for the resources. The Kubelet enforces those limits so that the running container is not allowed to use more of the resource than the limit set for it

Dashboard Metrics

Click Save to apply all the changes made to the Monitoring & Alerting add-ons

VM Operator (Optional)

By default, the VM Operator add-on is not enabled. Users can select VM Operator add-on to deploy KubeVirt components in the cluster to enable virtualization (or Kubevirt)

K8s Management Operator (mandatory)

A Kubernetes Management Operator is selected by default and users are not allowed to disable this add-on. K8 Operator is mandatory to deploy and manage the Kubernetes application. A Kubernetes application is both deployed on Kubernetes and managed using the Kubernetes API (application programming interface) and kubeCTL tooling

CSI Driver (Optional)

During the pod start/restart, CSI Driver communicates with the provider using gRPC to retrieve the secret content from the external Secrets Store specified in the SecretProviderClass custom resource. The AWS provider for the Secrets Store CSI Driver allows you to make secrets stored in Secrets Manager appear as files mounted in Kubernetes pods.

  • Click the Wrench icon to customize the CSI Driver parameters.

Customize CSI Driver Addons window appears


Only AWS provider is currently supported

  • Select the required parameters of the CSI Driver and close the window to save the changes

Managed System Add-Ons