{"id":5181,"date":"2026-11-18T21:23:22","date_gmt":"2026-11-18T21:23:22","guid":{"rendered":"https:\/\/bitflow-solutions.com\/guias-tecnicas\/grafana-prometheus-kubernetes-monitoring\/"},"modified":"2026-11-18T21:23:22","modified_gmt":"2026-11-18T21:23:22","slug":"grafana-prometheus-kubernetes-monitoring","status":"publish","type":"bf_guia","link":"https:\/\/bitflow-solutions.com\/en\/guias-tecnicas\/grafana-prometheus-kubernetes-monitoring\/","title":{"rendered":"Grafana and Prometheus on Kubernetes: monitoring on AKS, GKE, EKS and IONOS"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">A practical guide to setting up <strong>monitoring with Prometheus and Grafana<\/strong> on a managed Kubernetes cluster: <strong>AKS<\/strong> (Azure), <strong>GKE<\/strong> (Google Cloud), <strong>EKS<\/strong> (AWS) or <strong>IONOS Managed Kubernetes<\/strong>. With YAML manifests ready to adapt, credentials in Secrets, access only through the internal network and the differences between clouds. All the manifests and commands are also in the <strong>README.md<\/strong> on the left.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What you\u2019ll learn<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Deploying <strong>Prometheus<\/strong> and <strong>Grafana<\/strong> on Kubernetes with your own YAML manifests, without depending on a chart.<\/li>\n\n\n<li>Monitoring a service with <code>\/metrics<\/code> protected by username, password and HTTPS, and discovering pods automatically.<\/li>\n\n\n<li>Storing passwords and certificates in <strong>Secrets<\/strong>, not in ConfigMaps or in the YAML.<\/li>\n\n\n<li>Giving private access to Grafana on <strong>AKS<\/strong>, <strong>GKE<\/strong>, <strong>EKS<\/strong> and <strong>IONOS<\/strong>.<\/li>\n\n\n<li>Reloading the configuration, checking the status and solving the most common errors.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Prerequisites<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>An <strong>AKS<\/strong>, <strong>GKE<\/strong>, <strong>EKS<\/strong> or <strong>IONOS Managed Kubernetes<\/strong> cluster, and <code>kubectl<\/code> connected to it (see the Kubernetes administration guide).<\/li>\n\n\n<li>Permissions to create namespaces, ClusterRoles and persistent volumes.<\/li>\n\n\n<li><strong>Windows<\/strong> with <strong>PowerShell<\/strong>; <strong>Docker Desktop<\/strong> only to validate the configuration.<\/li>\n\n\n<li>On <strong>EKS<\/strong>, the <strong>Amazon EBS CSI driver<\/strong> add-on for the disks, and the <strong>AWS Load Balancer Controller<\/strong> if you are going to use an internal load balancer.<\/li>\n\n\n<li>The image versions are examples: always pin a specific version (never <code>latest<\/code>) and check the latest stable one in the Prometheus and Grafana release notes.<\/li>\n\n\n<li>If your cluster only pulls images from a private registry, copy <code>prom\/prometheus<\/code> and <code>grafana\/grafana<\/code> there and add its <code>imagePullSecrets<\/code>.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Step by step<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1. Prepare the namespace and check the storage<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Prometheus and Grafana store data on disk, so they need a persistent volume. Check that you are on the right cluster and which <strong>StorageClass<\/strong> will be used by default:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># The right cluster and a dedicated namespace for monitoring\nkubectl config current-context\nkubectl create namespace monitoring\n\n# Which StorageClass will be used for the disks (the one marked \"(default)\")\nkubectl get storageclass<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If none shows as <code>(default)<\/code>, add <code>storageClassName<\/code> to the <code>volumeClaimTemplates<\/code> in steps 5 and 6. On EKS, without the EBS CSI driver the volumes stay in <code>Pending<\/code>, and on new clusters <code>gp2<\/code> is no longer marked as the default.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Store the credentials in Secrets<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Passwords don\u2019t belong in the Prometheus ConfigMap or in the repository: anyone with read access to the namespace or to Git would see them. Create them as <strong>Secrets<\/strong> from local files, which you delete afterwards:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Password and certificate authority (CA) certificate of the service you are going to monitor\nkubectl create secret generic prometheus-target -n monitoring `\n  --from-file=password=.\\target-password.txt `\n  --from-file=ca.crt=.\\internal-ca.crt\n\n# Grafana administrator user and password\nkubectl create secret generic grafana-admin -n monitoring `\n  --from-literal=admin-user=admin `\n  --from-file=admin-password=.\\grafana-password.txt\n\n# Delete the local files with the passwords once the Secret has been created\nRemove-Item .\\target-password.txt, .\\grafana-password.txt<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For the service you are going to monitor, use a user that can only read metrics. If its certificate is signed by an internal CA, keep the <code>ca.crt<\/code>: that way Prometheus validates the certificate instead of skipping the check.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. Configure Prometheus<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The configuration goes in a ConfigMap. This example monitors three things: Prometheus itself, a service with protected <code>\/metrics<\/code> (with <code>password_file<\/code> and <code>ca_file<\/code>, which read the Secret from step 2) and the cluster pods that request it with annotations:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>apiVersion: v1\nkind: ConfigMap\nmetadata:\n  name: prometheus-config\n  namespace: monitoring\ndata:\n  prometheus.yml: |\n    global:\n      scrape_interval: 15s\n      evaluation_interval: 15s\n    scrape_configs:\n      # Prometheus itself\n      - job_name: prometheus\n        static_configs:\n          - targets: ['localhost:9090']\n\n      # A service with \/metrics protected by username and password, and HTTPS with its own CA\n      - job_name: my-service\n        scrape_interval: 30s\n        scheme: https\n        metrics_path: \/metrics\n        basic_auth:\n          username: metrics-reader\n          password_file: \/etc\/prometheus\/secrets\/password\n        tls_config:\n          ca_file: \/etc\/prometheus\/secrets\/ca.crt\n        static_configs:\n          - targets: ['metrics.my-company.internal:8443']\n\n      # Cluster pods that request it with prometheus.io\/* annotations\n      - job_name: pods\n        kubernetes_sd_configs:\n          - role: pod\n        relabel_configs:\n          - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_scrape]\n            action: keep\n            regex: \"true\"\n          - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_path]\n            action: replace\n            target_label: __metrics_path__\n            regex: (.+)\n          - source_labels: [__address__, __meta_kubernetes_pod_annotation_prometheus_io_port]\n            action: replace\n            regex: ([^:]+)(?::\\d+)?;(\\d+)\n            replacement: $1:$2\n            target_label: __address__\n          - source_labels: [__meta_kubernetes_namespace]\n            target_label: namespace\n          - source_labels: [__meta_kubernetes_pod_name]\n            target_label: pod<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">For Prometheus to monitor a pod, add <code>prometheus.io\/scrape: \"true\"<\/code>, <code>prometheus.io\/port<\/code> and, if it is not <code>\/metrics<\/code>, <code>prometheus.io\/path<\/code> to its template. Before applying it, validate the configuration with <code>promtool<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Validate the configuration before applying it (requires Docker Desktop)\n# Save the prometheus.yml block to a separate file for this check\ndocker run --rm -v \"${PWD}:\/cfg\" --entrypoint promtool prom\/prometheus:v3.2.1 check config \/cfg\/prometheus.yml<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">4. Grant read permissions to discover pods<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Pod discovery queries the Kubernetes API, so Prometheus needs its own service account with read-only permissions:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>apiVersion: v1\nkind: ServiceAccount\nmetadata:\n  name: prometheus\n  namespace: monitoring\n---\napiVersion: rbac.authorization.k8s.io\/v1\nkind: ClusterRole\nmetadata:\n  name: prometheus-read\nrules:\n  - apiGroups: [\"\"]\n    resources: [nodes, nodes\/metrics, services, endpoints, pods]\n    verbs: [get, list, watch]\n  - nonResourceURLs: [\/metrics]\n    verbs: [get]\n---\napiVersion: rbac.authorization.k8s.io\/v1\nkind: ClusterRoleBinding\nmetadata:\n  name: prometheus-read\nroleRef:\n  apiGroup: rbac.authorization.k8s.io\n  kind: ClusterRole\n  name: prometheus-read\nsubjects:\n  - kind: ServiceAccount\n    name: prometheus\n    namespace: monitoring<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">5. Deploy Prometheus<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A <strong>StatefulSet<\/strong> with its own disk, running without root privileges (the <code>nobody<\/code> user, 65534, from the official image), with health probes, memory limits and 15 days of retention. <code>--web.enable-lifecycle<\/code> lets you reload the configuration without restarting:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>apiVersion: v1\nkind: Service\nmetadata:\n  name: prometheus\n  namespace: monitoring\nspec:\n  selector:\n    app: prometheus\n  ports:\n    - name: web\n      port: 9090\n      targetPort: 9090\n---\napiVersion: apps\/v1\nkind: StatefulSet\nmetadata:\n  name: prometheus\n  namespace: monitoring\nspec:\n  serviceName: prometheus\n  replicas: 1\n  selector:\n    matchLabels:\n      app: prometheus\n  template:\n    metadata:\n      labels:\n        app: prometheus\n    spec:\n      serviceAccountName: prometheus\n      securityContext:\n        runAsNonRoot: true\n        runAsUser: 65534\n        runAsGroup: 65534\n        fsGroup: 65534\n      # nodeSelector:            # optional: a node pool dedicated to monitoring\n      #   pool: monitoring\n      containers:\n        - name: prometheus\n          image: prom\/prometheus:v3.2.1\n          args:\n            - --config.file=\/etc\/prometheus\/prometheus.yml\n            - --storage.tsdb.path=\/prometheus\n            - --storage.tsdb.retention.time=15d\n            - --web.enable-lifecycle\n          ports:\n            - containerPort: 9090\n          readinessProbe:\n            httpGet: { path: \/-\/ready, port: 9090 }\n          livenessProbe:\n            httpGet: { path: \/-\/healthy, port: 9090 }\n            initialDelaySeconds: 30\n          resources:\n            requests: { cpu: 250m, memory: 1Gi }\n            limits: { memory: 2Gi }\n          securityContext:\n            allowPrivilegeEscalation: false\n          volumeMounts:\n            - name: config\n              mountPath: \/etc\/prometheus\n            - name: secrets\n              mountPath: \/etc\/prometheus\/secrets\n              readOnly: true\n            - name: data\n              mountPath: \/prometheus\n      volumes:\n        - name: config\n          configMap:\n            name: prometheus-config\n        - name: secrets\n          secret:\n            secretName: prometheus-target\n  volumeClaimTemplates:\n    - metadata:\n        name: data\n      spec:\n        accessModes: [ReadWriteOnce]\n        resources:\n          requests:\n            storage: 20Gi<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The disk size depends on how many series you monitor and on the retention: start with 20 GB and keep an eye on usage (step 9).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">6. Deploy Grafana with Prometheus already configured<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Grafana reads the administrator user from the Secret and the data source from a <em>provisioning<\/em> file, so it starts already connected to Prometheus through its internal cluster name:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>apiVersion: v1\nkind: ConfigMap\nmetadata:\n  name: grafana-datasources\n  namespace: monitoring\ndata:\n  prometheus.yaml: |\n    apiVersion: 1\n    datasources:\n      - name: Prometheus\n        type: prometheus\n        access: proxy\n        url: http:\/\/prometheus.monitoring.svc.cluster.local:9090\n        isDefault: true\n---\napiVersion: v1\nkind: Service\nmetadata:\n  name: grafana\n  namespace: monitoring\nspec:\n  selector:\n    app: grafana\n  ports:\n    - name: web\n      port: 3000\n      targetPort: 3000\n---\napiVersion: apps\/v1\nkind: StatefulSet\nmetadata:\n  name: grafana\n  namespace: monitoring\nspec:\n  serviceName: grafana\n  replicas: 1\n  selector:\n    matchLabels:\n      app: grafana\n  template:\n    metadata:\n      labels:\n        app: grafana\n    spec:\n      securityContext:\n        runAsNonRoot: true\n        runAsUser: 472\n        fsGroup: 472\n      containers:\n        - name: grafana\n          image: grafana\/grafana:11.6.0\n          ports:\n            - containerPort: 3000\n          env:\n            - name: GF_SECURITY_ADMIN_USER\n              valueFrom:\n                secretKeyRef: { name: grafana-admin, key: admin-user }\n            - name: GF_SECURITY_ADMIN_PASSWORD\n              valueFrom:\n                secretKeyRef: { name: grafana-admin, key: admin-password }\n          readinessProbe:\n            httpGet: { path: \/api\/health, port: 3000 }\n          resources:\n            requests: { cpu: 100m, memory: 256Mi }\n            limits: { memory: 512Mi }\n          securityContext:\n            allowPrivilegeEscalation: false\n          volumeMounts:\n            - name: data\n              mountPath: \/var\/lib\/grafana\n            - name: datasources\n              mountPath: \/etc\/grafana\/provisioning\/datasources\n              readOnly: true\n      volumes:\n        - name: datasources\n          configMap:\n            name: grafana-datasources\n  volumeClaimTemplates:\n    - metadata:\n        name: data\n      spec:\n        accessModes: [ReadWriteOnce]\n        resources:\n          requests:\n            storage: 5Gi<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Apply everything and wait for the pods to be ready:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>kubectl apply -f .\\prometheus-config.yaml\nkubectl apply -f .\\prometheus-rbac.yaml\nkubectl apply -f .\\prometheus.yaml\nkubectl apply -f .\\grafana.yaml\n\nkubectl get pods,pvc,svc -n monitoring\nkubectl rollout status statefulset\/prometheus -n monitoring\nkubectl rollout status statefulset\/grafana -n monitoring<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">7. Access Grafana securely<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">To start with, you don\u2019t need to expose anything: <code>kubectl port-forward<\/code> opens a tunnel from your machine, authenticated with your cluster credentials:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Grafana at http:\/\/localhost:3000 (username and password from the grafana-admin Secret)\nkubectl port-forward svc\/grafana 3000:3000 -n monitoring\n\n# Prometheus at http:\/\/localhost:9090 (Status &gt; Targets: all targets UP)\nkubectl port-forward svc\/prometheus 9090:9090 -n monitoring<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">In Grafana, go to <strong>Explore<\/strong>, choose Prometheus and query <code>up<\/code>: each monitored target appears with value 1 if it responds.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">8. Publish Grafana on the internal network only<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">When the team needs access without <code>kubectl<\/code>, use an <strong>internal<\/strong> load balancer, with a private IP on the cluster network, and also restrict which networks can connect:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>apiVersion: v1\nkind: Service\nmetadata:\n  name: grafana-internal\n  namespace: monitoring\n  annotations:\n    # Only the line for your cloud:\n    service.beta.kubernetes.io\/azure-load-balancer-internal: \"true\"        # AKS\n    # networking.gke.io\/load-balancer-type: \"Internal\"                     # GKE\n    # service.beta.kubernetes.io\/aws-load-balancer-type: \"external\"        # EKS (AWS Load Balancer Controller)\n    # service.beta.kubernetes.io\/aws-load-balancer-nlb-target-type: \"ip\"   # EKS\n    # service.beta.kubernetes.io\/aws-load-balancer-scheme: \"internal\"      # EKS (already the default value)\nspec:\n  type: LoadBalancer\n  loadBalancerSourceRanges:\n    - 10.20.0.0\/16          # only your office network or your VPN, never 0.0.0.0\/0\n  selector:\n    app: grafana\n  ports:\n    - name: web\n      port: 3000\n      targetPort: 3000<\/code><\/pre>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Cloud<\/th><th>Internal load balancer<\/th><th>Notes<\/th><\/tr><\/thead><tbody><tr><td>AKS<\/td><td><code>azure-load-balancer-internal: \"true\"<\/code><\/td><td>Private IP on the cluster VNet.<\/td><\/tr><tr><td>GKE<\/td><td><code>networking.gke.io\/load-balancer-type: \"Internal\"<\/code><\/td><td>Private IP on the VPC.<\/td><\/tr><tr><td>EKS<\/td><td><code>aws-load-balancer-scheme: \"internal\"<\/code> with the AWS Load Balancer Controller<\/td><td>Creates an internal Network Load Balancer.<\/td><\/tr><tr><td>IONOS<\/td><td>There is no internal load balancer for Services<\/td><td><code>LoadBalancer<\/code> Services only work on public node pools and attach a fixed public IP to a node: for Grafana, <code>port-forward<\/code> or an Ingress with TLS and restricted access is a better option.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><code>loadBalancerSourceRanges<\/code> restricts the source IPs: GKE applies it on internal and external load balancers; on EKS it only takes effect if the load balancer preserves the client IP (with <code>nlb-target-type: \"ip\"<\/code> this is disabled by default). On any cloud, reinforce it with network rules (NSG, VPC firewall or security groups).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Never publish Grafana or Prometheus with <code>0.0.0.0\/0<\/code>: Prometheus has no username or password by default, and anyone who reaches it can read all the metrics.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">9. Day-to-day operations<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">To change what is monitored, edit the ConfigMap, apply it and ask Prometheus to reload. Here you also have how to check the status, read the logs and keep an eye on disk space:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Change the Prometheus configuration without restarting it\nkubectl apply -f .\\prometheus-config.yaml\n# (wait about a minute for the pod to see the new ConfigMap)\nkubectl port-forward svc\/prometheus 9090:9090 -n monitoring\ncurl.exe -X POST http:\/\/localhost:9090\/-\/reload      # in another PowerShell window\n\n# Check the status\ncurl.exe http:\/\/localhost:9090\/-\/ready\nkubectl logs statefulset\/prometheus -n monitoring --tail=50\nkubectl logs statefulset\/grafana -n monitoring --tail=50\n\n# Prometheus disk space\nkubectl exec prometheus-0 -n monitoring -- df -h \/prometheus<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If the reload fails, Prometheus keeps the previous configuration and says so in its logs: fix the error and reload again.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Common errors<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">The target shows as DOWN with \u201cx509: certificate signed by unknown authority\u201d<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Prometheus does not trust the service certificate. Add the CA that signs it in <code>tls_config.ca_file<\/code> (step 2). Don\u2019t use <code>insecure_skip_verify: true<\/code>: anyone could then impersonate the service and receive the password.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The target shows as DOWN with \u201c401 Unauthorized\u201d<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The username or password is wrong, or the file has a trailing line break. Create the Secret again with <code>kubectl create secret \u2026 --dry-run=client -o yaml | kubectl apply -f -<\/code> and restart the pod.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The pod stays in Pending<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">It is usually the volume: <code>kubectl describe pvc -n monitoring<\/code> tells you why. There is no default StorageClass, the EBS CSI driver is missing on EKS, or the <code>nodeSelector<\/code> does not match any node.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">CrashLoopBackOff with \u201cpermission denied\u201d on \/prometheus or \/var\/lib\/grafana<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The disk does not have permissions for the container user. Check that the pod\u2019s <code>securityContext<\/code> includes <code>fsGroup<\/code> (65534 for Prometheus, 472 for Grafana).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Grafana cannot connect to Prometheus<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Check the data source URL: inside the cluster it is <code>http:\/\/prometheus.monitoring.svc.cluster.local:9090<\/code>, never <code>localhost<\/code>. Also check that the Prometheus pod is ready.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The load balancer stays with EXTERNAL-IP \u201cpending\u201d<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The cloud could not create it: look at the events with <code>kubectl describe svc grafana-internal -n monitoring<\/code>. On EKS, check that the AWS Load Balancer Controller is installed; on IONOS, that the node pool is public.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Annotated pods do not appear in Targets<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The RBAC from step 4 is missing (the Prometheus logs show \u201cforbidden\u201d), or the annotations are on the Deployment rather than on the pod template. The value of <code>prometheus.io\/scrape<\/code> must be the text <code>\"true\"<\/code>, in quotes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Next steps<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Define alerts with <strong>Alertmanager<\/strong> (for example, target down or disk almost full) and send them to the team\u2019s channel.<\/li>\n\n\n<li>Monitor the cluster itself with <strong>kube-state-metrics<\/strong> and <strong>node-exporter<\/strong>, or move to the <strong>kube-prometheus-stack<\/strong> Helm chart when you need the whole set.<\/li>\n\n\n<li>Store the Grafana dashboards as code (dashboard provisioning) in the repository.<\/li>\n\n\n<li>For long retention or several clusters, consider a managed Prometheus service from your cloud, or Thanos or Mimir.<\/li>\n\n\n<li>Deploy the manifests from a pipeline (see the CI\/CD with GitHub Actions guide).<\/li>\n\n<\/ul>\n\n\n","protected":false},"excerpt":{"rendered":"<p>How to deploy Prometheus and Grafana on a managed cluster with YAML manifests: credentials in Secrets, pod discovery, access through the internal network on each cloud and the most common errors.<\/p>\n","protected":false},"featured_media":0,"template":"","bf_tecnologia":[103,104,106],"bf_nivel":[109],"class_list":["post-5181","bf_guia","type-bf_guia","status-publish","hentry","bf_tecnologia-cloud-en","bf_tecnologia-devops-en","bf_tecnologia-monitoring","bf_nivel-intermediate"],"acf":[],"_links":{"self":[{"href":"https:\/\/bitflow-solutions.com\/en\/wp-json\/wp\/v2\/bf_guia\/5181","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bitflow-solutions.com\/en\/wp-json\/wp\/v2\/bf_guia"}],"about":[{"href":"https:\/\/bitflow-solutions.com\/en\/wp-json\/wp\/v2\/types\/bf_guia"}],"version-history":[{"count":0,"href":"https:\/\/bitflow-solutions.com\/en\/wp-json\/wp\/v2\/bf_guia\/5181\/revisions"}],"wp:attachment":[{"href":"https:\/\/bitflow-solutions.com\/en\/wp-json\/wp\/v2\/media?parent=5181"}],"wp:term":[{"taxonomy":"bf_tecnologia","embeddable":true,"href":"https:\/\/bitflow-solutions.com\/en\/wp-json\/wp\/v2\/bf_tecnologia?post=5181"},{"taxonomy":"bf_nivel","embeddable":true,"href":"https:\/\/bitflow-solutions.com\/en\/wp-json\/wp\/v2\/bf_nivel?post=5181"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}