charts VS metrics-server

I'm using this prometheus helm chart.

I did this using the incubator/raw chart ( https://github.com/helm/charts/tree/master/incubator/raw ), by creating a k8s Job.

I've installed Prometheus operator 0.34 (which works as expected) on cluster A (main prom)Now I want to use the federation option,I mean collect metrics from other Prometheus which is located on other K8S cluster B

So I am using the helm chart stable/traefik to deploy a reverse proxy to my cluster. I need to customise it beyond what is possible with the variables I can set for the template.

It may be that we just migrated to Bitnami's chart when the old "stable" chart was deprecated

Edit: I'm using Postgresql Stable Chart version 5.3.10

I'm using the official stable/prometheus-operator chart do deploy Prometheus with helm.

I am using using https://github.com/helm/charts/tree/master/stable/airflow helm chart and building v1.10.8 puckle/docker-airflow image with kubernetes installed on it and using that image in the helm chart,But I keep getting

# patches/metrics-server.yaml machine: kubelet: extraArgs: rotate-server-certificates: true files: - content: | [metrics] address = "0.0.0.0:11234" path: /var/cri/conf.d/metrics.toml op: create cluster: extraManifests: - https://raw.githubusercontent.com/alex1989hu/kubelet-serving-cert-approver/main/deploy/standalone-install.yaml - https://github.com/kubernetes-sigs/metrics-server/releases/latest/download/components.yaml

Kube-State-Metrics is only one part of the Kubernetes metrics ecosystem. Metrics-Server is another commonly discussed component that you should also include in your observability strategy. Whereas Kube-State-Metrics reports metrics about the states of objects in your cluster, Metrics-Server exposes real-time CPU and memory resource utilization metrics for your Nodes and Pods.

apiVersion: metal.sidero.dev/v1alpha1 kind: ServerClass metadata: name: masters spec: qualifiers: hardware: - system: manufacturer: QEMU memory: totalSize: "12 GB" configPatches: - op: add path: /machine/network/interfaces value: - deviceSelector: busPath: "0*" dhcp: true vip: ip: "10.1.1.50" - op: add path: /machine/network/nameservers value: - 1.1.1.1 - 1.0.0.1 - op: replace path: /machine/install value: disk: none diskSelector: size: '< 100GB' - op: replace path: /cluster/network/cni value: name: none # name: "custom" # urls: # - "https://raw.githubusercontent.com/kubebn/talos-proxmox-kaas/main/manifests/talos/cilium.yaml" - op: replace path: /cluster/proxy value: disabled: true - op: replace path: /machine/kubelet/extraArgs value: rotate-server-certificates: true - op: replace path: /cluster/inlineManifests value: - name: cilium contents: |- apiVersion: v1 kind: Namespace metadata: name: cilium labels: pod-security.kubernetes.io/enforce: "privileged" - op: replace path: /cluster/extraManifests value: - https://github.com/kubernetes-sigs/metrics-server/releases/latest/download/components.yaml - https://raw.githubusercontent.com/alex1989hu/kubelet-serving-cert-approver/main/deploy/standalone-install.yaml

Just add `--kubelet-insecure-tls`

that solves the problem!

https://github.com/kubernetes-sigs/metrics-server/issues/196

Before deploying anything into this namespace, it’s important first to verify that the metrics server is deployed and configured in your cluster. This metrics server is part of how Kubernetes implements autoscaling rules. Check whether it’s installed by running:

Metrics Server is a Kubernetes addon that collects CPU and memory resource utilization information at the Node and Pod level. It's a lightweight, single-cluster, Kubernetes-only alternative to more complex monitoring solutions like Prometheus.

(kubespray-venv) kube-master1:~# curl -LO https://github.com/kubernetes-sigs/metrics-server/releases/latest/download/components.yaml nano components.yaml

The last one is mostly an observability stack with Prometheus, Metric server, and Prometheus adapter to have excellent insights into what is happening on the cluster. You can reuse the same stack for autoscaling by repurposing all the data collected for monitoring.

and the Metrics Server.

Metrics-server is installed by default on OVH, and has to be installed manually on AWS/EKS cluster.