Reading and writing Yandex Managed Service for Kubernetes cluster metrics with Prometheus Operator

Prometheus Operator with Yandex Monitoring support streamlines the installation of Prometheus Operator, a popular solution for Kubernetes cluster monitoring, providing integration with Yandex Monitoring. You can use it to collect, store, and read metrics from containers, applications, and the infrastructure. The system leverages the Prometheus data model and PromQL.

Getting startedGetting started

1. Make sure that the security groups for the Managed Service for Kubernetes cluster and its node groups are configured correctly. If any rule is missing, add it.

   Warning

   The configuration of security groups determines the performance and availability of the cluster and the services and applications running in it.

2. Create a service account with the monitoring.editor role.

3. Create an API key for the service account:

   • If you want to install Prometheus Operator using Yandex Cloud Marketplace, create an API key in JSON format and save it to the sa-key.json file:

     yc iam api-key create \
        --service-account-name=<service_account_name> \
        --format=json | jq -c > sa-key.json
     

     Tip

     You can also automatically create a new API key during the app installation.

   • If you want to install Prometheus Operator using a Helm chart, run the following command and save the secret key you get:

     yc iam api-key create --service-account-name=<service_account_name>
     

4. Install kubect and configure it to work with the new cluster.

5. If you do not have a Prometheus workspace yet, create one:

   Management console

   1. Open the Monitoring home page.
   2. In the left-hand panel, select Prometheus.
   3. Click Create workspace.

Installation from Yandex Cloud MarketplaceInstallation from Yandex Cloud Marketplace

Installation using a Helm chartInstallation using a Helm chart

1. Install Helm v3.8.0 or higher.

2. Get the Prometheus workspace ID:

   Management console

   1. Open the Monitoring home page.
   2. Select Prometheus on the left.
   3. Select a Prometheus workspace.
   4. This will open the General information tab displaying the workspace ID. Save the ID.

3. To install a Helm chart with Prometheus Operator, run this command:

   helm pull oci://cr.yandex/yc-marketplace/yandex-cloud/prometheus/kube-prometheus-stack \
     --version 72.6.2-1 \
     --untar && \
   helm install \
     --namespace <namespace_for_Prometheus_Operator> \
     --create-namespace \
     --set prometheusWorkspaceId=<Prometheus_workspace_ID> \
     --set iam_api_key_value_generated.secretAccessKey=<secret_part_of_API_key> \
     prometheus ./kube-prometheus-stack/
   

   This command will also create a new namespace for Prometheus Operator.

   If you set namespace to the default namespace, Prometheus Operator may work incorrectly. Use a value different from all the existing namespaces, e.g., prometheus-operator-space.

   Note

   If you are using a Helm version below 3.8.0, append the export HELM_EXPERIMENTAL_OCI=1 && \ string to the command to enable Open Container Initiative (OCI) support in the Helm client.

4. Make sure the Prometheus Operator pods have changed their status to Running:

   kubectl get pods --namespace=<namespace_for_Prometheus_Operator> \
      -l "release=prometheus"
   

Viewing charts based on metricsViewing charts based on metrics

Adding charts to dashboardsAdding charts to dashboards

(Optional) Configuring alerts based on metrics(Optional) Configuring alerts based on metrics

1. Create a notification channel by selecting an available sending method.

2. Set up the Alert Manager responsible for sending notifications:

   1. Open the Monitoring home page.

   2. Select Prometheus on the left.

   3. Select a Prometheus workspace.

   4. Navigate to the Alert manager configuration tab.

   5. Click Upload a configuration file and upload the configuration file in YAML format.

      Sample configuration file

      global:
        resolve_timeout: 5m
      route:
        receiver: telegram
        routes:
          - receiver: "null"
            matchers:
              - severity="none"
            continue: false
      
      receivers:
        - name: telegram
          yandex_monitoring_configs:
            - channel_names:
              - "<notification_channel_name>"
        - name: "null"
          yandex_monitoring_configs:
            - channel_names: []
      

3. Add a test alerting rule:

   cat <<EOF | kubectl apply -f -
   apiVersion: monitoring.coreos.com/v1                                                        
   kind: PrometheusRule
   metadata:
     labels:
       release: kube-prometheus-stack
     name: test
   spec:
     groups:
     - name: test
       rules:
         - alert: Test
           annotations:
             description: this is a test alert
             summary: test alert
           expr: vector(1)
           labels:
             severity: warning
   EOF
   

4. Wait until you get alerted through the selected notification channel or check the alert status in the management console:

   1. Open the Monitoring home page.
   2. Select Prometheus on the left.
   3. Select a Prometheus workspace.
   4. Navigate to the Managing rules tab.
   5. Click the test alert name.
   6. Navigate to the Alerts tab.
   7. Make sure the test alert status changed to FIRING.

See alsoSee also

• Yandex Managed Service for Kubernetes

© 2025 Linux Foundation. All rights reserved. The Linux Foundation owns and uses registered trademarks. For a list of Linux Foundation trademarks, see Trademark Usage.