Prometheus Adapter serves as a bridge between Kubernetes metrics and Prometheus. Which option best describes this role?

Prometheus Adapter serves as a bridge between Kubernetes metrics and Prometheus. Which option best describes this role?

• A. It stores metrics in etcd
• B. It adapts Kubernetes information to Prometheus metrics
• C. It scrapes endpoints
• D. It visualizes metrics in Grafana

Answer: (B)

The Prometheus Adapter is about translating and exposing metrics from Prometheus to Kubernetes. It sits between the Kubernetes Metrics API and Prometheus, so when Kubernetes asks for a metric, the adapter converts that request into a PromQL query against Prometheus, retrieves the result, and returns it in the format Kubernetes expects. This lets Kubernetes components (like the Horizontal Pod Autoscaler) use Prometheus-backed metrics as if they were native Kubernetes metrics, without Prometheus having to push data into Kubernetes or Kubernetes needing to know Prometheus specifics. It doesn’t store metrics in etcd, which is Kubernetes’ data store. It doesn’t scrape endpoints itself (that’s Prometheus’s job). It doesn’t visualize metrics (that’s Grafana’s role, which reads from Prometheus).

The Prometheus Adapter is about translating and exposing metrics from Prometheus to Kubernetes. It sits between the Kubernetes Metrics API and Prometheus, so when Kubernetes asks for a metric, the adapter converts that request into a PromQL query against Prometheus, retrieves the result, and returns it in the format Kubernetes expects. This lets Kubernetes components (like the Horizontal Pod Autoscaler) use Prometheus-backed metrics as if they were native Kubernetes metrics, without Prometheus having to push data into Kubernetes or Kubernetes needing to know Prometheus specifics.

It doesn’t store metrics in etcd, which is Kubernetes’ data store. It doesn’t scrape endpoints itself (that’s Prometheus’s job). It doesn’t visualize metrics (that’s Grafana’s role, which reads from Prometheus).