Prometheus

 

1. Prometheus ConfigMap

This ConfigMap contains the configuration for Prometheus, defining which services it will scrape metrics from.

apiVersion: v1

kind: ConfigMap

metadata:

  name: prometheus-config

  namespace: monitoring

  labels:

    app: prometheus

data:

  prometheus.yml: |

    global:

      scrape_interval: 15s

    scrape_configs:

      - job_name: 'kubernetes-apiservers'

        kubernetes_sd_configs:

        - role: endpoints

        scheme: https

        tls_config:

          ca_file: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt

          insecure_skip_verify: true

        bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token

        relabel_configs:

        - source_labels: [__meta_kubernetes_namespace, __meta_kubernetes_service_name, __meta_kubernetes_endpoint_port_name]

          action: keep

          regex: default;kubernetes;https


      - job_name: 'kubernetes-nodes'

        kubernetes_sd_configs:

        - role: node

        relabel_configs:

        - action: labelmap

          regex: __meta_kubernetes_node_label_(.+)


      - job_name: 'kubernetes-pods'

        kubernetes_sd_configs:

        - role: pod

        relabel_configs:

        - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_scrape]

          action: keep

          regex: true

        - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_path]

          action: replace

          target_label: __metrics_path__

          regex: (.+)

        - source_labels: [__address__, __meta_kubernetes_pod_annotation_prometheus_io_port]

          action: replace

          regex: ([^:]+)(?::\d+)?;(\d+)

          replacement: $1:$2

          target_label: __address__



2. Prometheus Deployment

This Deployment manages the Prometheus Pods.

apiVersion: apps/v1

kind: Deployment

metadata:

  name: prometheus-deployment

  namespace: monitoring

  labels:

    app: prometheus

spec:

  replicas: 1

  selector:

    matchLabels:

      app: prometheus

  template:

    metadata:

      labels:

        app: prometheus

    spec:

      containers:

      - name: prometheus

        image: prom/prometheus:v2.30.0

        args:

        - "--config.file=/etc/prometheus/prometheus.yml"

        - "--storage.tsdb.path=/prometheus/"

        - "--web.console.libraries=/usr/share/prometheus/console_libraries"

        - "--web.console.templates=/usr/share/prometheus/consoles"

        ports:

        - containerPort: 9090

        volumeMounts:

        - name: prometheus-config-volume

          mountPath: /etc/prometheus/

        - name: prometheus-storage-volume

          mountPath: /prometheus/

      volumes:

      - name: prometheus-config-volume

        configMap:

          name: prometheus-config

      - name: prometheus-storage-volume

        emptyDir: {}


3. Prometheus Service

This Service exposes Prometheus to be accessed within the cluster or externally.

apiVersion: v1

kind: Service

metadata:

  name: prometheus-service

  namespace: monitoring

  labels:

    app: prometheus

spec:

  type: NodePort

  ports:

  - port: 9090

    targetPort: 9090

    nodePort: 30000

  selector:

    app: prometheus



4. Namespace (Optional)

Create a separate namespace for monitoring if you haven't already.

apiVersion: v1

kind: Namespace

metadata:

  name: monitoring


5. Apply the YAML Files

  1. Create the Namespace:
    kubectl apply -f namespace.yaml

  2. Apply the ConfigMap:
          kubectl apply -f prometheus-config.yaml
    
      3. Apply the Deployment:

        kubectl apply -f prometheus-deployment.yaml

       4. Apply the Service:

          kubectl apply -f prometheus-service.yaml


Access Prometheus

You can access Prometheus using the NodePort service on http://<node-ip>:30000.

This setup provides a basic Prometheus deployment for monitoring Kubernetes clusters. You can extend this by adding more scrape configs, setting up persistent storage, or integrating it with Grafana for better visualization.

Comments

Post a Comment

Popular posts from this blog

Delploy Cluster : Managed K8 & Self Managed K8

Self Managed K8 & Managed K8  In a self-managed Kubernetes cluster, the user is responsible for managing almost every aspect of the cluster. Here are the main components that need to be managed by users: 1. Control Plane Components : Kube-apiserver : The API server is the central management point of the Kubernetes cluster. Users are responsible for setting up, configuring, and managing its availability and performance. Etcd : The key-value store used by Kubernetes for all cluster data. Users need to manage the deployment, backup, scaling, and recovery of etcd . Kube-scheduler : This component is responsible for scheduling pods on available nodes. Users manage its configuration and ensure it runs reliably. Kube-controller-manager : This component runs controller processes that handle replication, node management, endpoints, etc. Users are responsible for managing these controllers. 2. Worker Nodes Components : Kubelet : This agent runs on each worker node and is responsible for ...
Read more

ctr | nerdctl | crictl

The Open Container Initiative (OCI) is a project under the Linux Foundation that aims to create open standards for container formats and runtimes. It was established in June 2015 by Docker, CoreOS, and other leaders in the container industry OCI has developed three key specifications: Runtime Specification (runtime-spec) : Defines how to run a container's filesystem bundle. Image Specification (image-spec) : Standardizes the format for container images. Distribution Specification (distribution-spec) : Provides an API protocol for distributing container content  The initiative also includes tools like runc , which is a reference implementation of the runtime-spec ctr, nerdctl, and crictl: Understanding Their Roles in the Container Ecosystem When working with containers, there are several tools available for interacting with container runtimes like containerd and Kubernetes. ctr , nerdctl , and crictl are three such tools, each serving different purposes within the container life...
Read more

Deploy To Kubernetes with Jenkins GitOps GitHub Pipeline

Image
 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ https://www.youtube.com/watch?v=o4QG_kqYvHk  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Basic Jenkins file for the pipeline. Docker image creation and building pipeline {     agent any     environment {         ECR_REPOSITORY = 'your-ecr-repository'         GITOPS_REPO_URL = 'https://github.com/your-gitops-repo.git'         GITOPS_REPO_CREDENTIALS = credentials('your-gitops-credentials-id')     }     stages {         stage('Build Docker Image') {             steps {                 script {         ...
Read more