Kubernetes部署Prometheus

已于 2024-02-21 14:42:01 修改
阅读量652 收藏 8
点赞数 8
文章标签： docker 容器 运维
于 2024-02-19 18:47:06 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/SYHbb11/article/details/136173007
版权

1、下载git

yum -y install git

2、拉取prometheus

git clone https://github.com/prometheus-operator/kube-prometheus.git -b release-0.11

   ### kubenetes的版本为：kubectl version ----- "v1.23.6"

   ###拉取完成后在:当前路径下的kube-prometheus中
cd kube-prometheus/

 
   ### 注：在release-0.11版本之后新增了NetworkPolicy
       默认是允许自己访问，如果了解NetworkPolicy可以修改一下默认的规则，可以用查看 ls *networkPolicy*，如果不修改的话则会影响到修改NodePort类型也无法访问
       不会Networkpolicy可以直接删除/备份

cd kube-prometheus/manifests
ls *networkPolicy*
mv *networkPolicy.yaml /tmp    #移动到tmp目录下，备份

3、查看namespace

cd kube-prometheus/manifests/setup

cat namespace.yaml

   apiVersion: v1
   kind: Namespace
   metadata:
     name: monitoring

### 使用monitoring的网络命名空间

4、安装部署

[root@master kube-prometheus]# 
kubectl apply --server-side -f manifests/setup
until kubectl get servicemonitors --all-namespaces ; do date; sleep 1; echo ""; done
kubectl apply -f manifests/



### [root@master kube-prometheus]# kubectl apply --server-side -f manifests/setup
customresourcedefinition.apiextensions.k8s.io/alertmanagerconfigs.monitoring.coreos.com serverside-applied
customresourcedefinition.apiextensions.k8s.io/alertmanagers.monitoring.coreos.com serverside-applied
customresourcedefinition.apiextensions.k8s.io/podmonitors.monitoring.coreos.com serverside-applied
customresourcedefinition.apiextensions.k8s.io/probes.monitoring.coreos.com serverside-applied
customresourcedefinition.apiextensions.k8s.io/prometheuses.monitoring.coreos.com serverside-applied
customresourcedefinition.apiextensions.k8s.io/prometheusrules.monitoring.coreos.com serverside-applied
customresourcedefinition.apiextensions.k8s.io/servicemonitors.monitoring.coreos.com serverside-applied
customresourcedefinition.apiextensions.k8s.io/thanosrulers.monitoring.coreos.com serverside-applied
namespace/monitoring serverside-applied

### [root@master kube-prometheus]# until kubectl get servicemonitors --all-namespaces ; do date; sleep 1; echo ""; done
No resources found

### [root@master kube-prometheus]# kubectl apply -f manifests/
alertmanager.monitoring.coreos.com/main created
networkpolicy.networking.k8s.io/alertmanager-main created
poddisruptionbudget.policy/alertmanager-main created
prometheusrule.monitoring.coreos.com/alertmanager-main-rules created
secret/alertmanager-main created
service/alertmanager-main created
serviceaccount/alertmanager-main created
servicemonitor.monitoring.coreos.com/alertmanager-main created
clusterrole.rbac.authorization.k8s.io/blackbox-exporter created
clusterrolebinding.rbac.authorization.k8s.io/blackbox-exporter created
configmap/blackbox-exporter-configuration created
deployment.apps/blackbox-exporter created
networkpolicy.networking.k8s.io/blackbox-exporter created
service/blackbox-exporter created
serviceaccount/blackbox-exporter created
servicemonitor.monitoring.coreos.com/blackbox-exporter created
secret/grafana-config created
secret/grafana-datasources created
configmap/grafana-dashboard-alertmanager-overview created
configmap/grafana-dashboard-apiserver created
configmap/grafana-dashboard-cluster-total created
configmap/grafana-dashboard-controller-manager created
configmap/grafana-dashboard-grafana-overview created
configmap/grafana-dashboard-k8s-resources-cluster created
configmap/grafana-dashboard-k8s-resources-namespace created
configmap/grafana-dashboard-k8s-resources-node created
configmap/grafana-dashboard-k8s-resources-pod created
configmap/grafana-dashboard-k8s-resources-workload created
configmap/grafana-dashboard-k8s-resources-workloads-namespace created
configmap/grafana-dashboard-kubelet created
configmap/grafana-dashboard-namespace-by-pod created
configmap/grafana-dashboard-namespace-by-workload created
configmap/grafana-dashboard-node-cluster-rsrc-use created
configmap/grafana-dashboard-node-rsrc-use created
configmap/grafana-dashboard-nodes created
configmap/grafana-dashboard-persistentvolumesusage created
configmap/grafana-dashboard-pod-total created
configmap/grafana-dashboard-prometheus-remote-write created
configmap/grafana-dashboard-prometheus created
configmap/grafana-dashboard-proxy created
configmap/grafana-dashboard-scheduler created
configmap/grafana-dashboard-workload-total created
configmap/grafana-dashboards created
deployment.apps/grafana created
networkpolicy.networking.k8s.io/grafana created
prometheusrule.monitoring.coreos.com/grafana-rules created
service/grafana created
serviceaccount/grafana created
servicemonitor.monitoring.coreos.com/grafana created
prometheusrule.monitoring.coreos.com/kube-prometheus-rules created
clusterrole.rbac.authorization.k8s.io/kube-state-metrics created
clusterrolebinding.rbac.authorization.k8s.io/kube-state-metrics created
deployment.apps/kube-state-metrics created
networkpolicy.networking.k8s.io/kube-state-metrics created
prometheusrule.monitoring.coreos.com/kube-state-metrics-rules created
service/kube-state-metrics created
serviceaccount/kube-state-metrics created
servicemonitor.monitoring.coreos.com/kube-state-metrics created
prometheusrule.monitoring.coreos.com/kubernetes-monitoring-rules created
servicemonitor.monitoring.coreos.com/kube-apiserver created
servicemonitor.monitoring.coreos.com/coredns created
servicemonitor.monitoring.coreos.com/kube-controller-manager created
servicemonitor.monitoring.coreos.com/kube-scheduler created
servicemonitor.monitoring.coreos.com/kubelet created
clusterrole.rbac.authorization.k8s.io/node-exporter created
clusterrolebinding.rbac.authorization.k8s.io/node-exporter created
daemonset.apps/node-exporter created
networkpolicy.networking.k8s.io/node-exporter created
prometheusrule.monitoring.coreos.com/node-exporter-rules created
service/node-exporter created
serviceaccount/node-exporter created
servicemonitor.monitoring.coreos.com/node-exporter created
clusterrole.rbac.authorization.k8s.io/prometheus-k8s created
clusterrolebinding.rbac.authorization.k8s.io/prometheus-k8s created
networkpolicy.networking.k8s.io/prometheus-k8s created
poddisruptionbudget.policy/prometheus-k8s created
prometheus.monitoring.coreos.com/k8s created
prometheusrule.monitoring.coreos.com/prometheus-k8s-prometheus-rules created
rolebinding.rbac.authorization.k8s.io/prometheus-k8s-config created
rolebinding.rbac.authorization.k8s.io/prometheus-k8s created
rolebinding.rbac.authorization.k8s.io/prometheus-k8s created
rolebinding.rbac.authorization.k8s.io/prometheus-k8s created
role.rbac.authorization.k8s.io/prometheus-k8s-config created
role.rbac.authorization.k8s.io/prometheus-k8s created
role.rbac.authorization.k8s.io/prometheus-k8s created
role.rbac.authorization.k8s.io/prometheus-k8s created
service/prometheus-k8s created
serviceaccount/prometheus-k8s created
servicemonitor.monitoring.coreos.com/prometheus-k8s created
apiservice.apiregistration.k8s.io/v1beta1.metrics.k8s.io created
clusterrole.rbac.authorization.k8s.io/prometheus-adapter created
clusterrole.rbac.authorization.k8s.io/system:aggregated-metrics-reader created
clusterrolebinding.rbac.authorization.k8s.io/prometheus-adapter created
clusterrolebinding.rbac.authorization.k8s.io/resource-metrics:system:auth-delegator created
clusterrole.rbac.authorization.k8s.io/resource-metrics-server-resources created
configmap/adapter-config created
deployment.apps/prometheus-adapter created
networkpolicy.networking.k8s.io/prometheus-adapter created
poddisruptionbudget.policy/prometheus-adapter created
rolebinding.rbac.authorization.k8s.io/resource-metrics-auth-reader created
service/prometheus-adapter created
serviceaccount/prometheus-adapter created
servicemonitor.monitoring.coreos.com/prometheus-adapter created
clusterrole.rbac.authorization.k8s.io/prometheus-operator created
clusterrolebinding.rbac.authorization.k8s.io/prometheus-operator created
deployment.apps/prometheus-operator created
networkpolicy.networking.k8s.io/prometheus-operator created
prometheusrule.monitoring.coreos.com/prometheus-operator-rules created
service/prometheus-operator created
serviceaccount/prometheus-operator created
servicemonitor.monitoring.coreos.com/prometheus-operator created

5、查看是否都running：

[root@master manifests]# kubectl get pod  -n monitoring
NAME                                  READY   STATUS             RESTARTS   AGE
alertmanager-main-0                   2/2     Running            0          22m
alertmanager-main-1                   2/2     Running            0          22m
alertmanager-main-2                   2/2     Running            0          22m
blackbox-exporter-746c64fd88-dk4qt    3/3     Running            0          23m
grafana-5fc7f9f55d-n7szn              1/1     Running            0          23m
kube-state-metrics-6c8846558c-d8j62   2/3     ImagePullBackOff   0          23m
node-exporter-h7f27                   2/2     Running            0          23m
node-exporter-j8lhq                   2/2     Running            0          23m
node-exporter-w65kk                   2/2     Running            0          23m
prometheus-adapter-6455646bdc-8c26s   0/1     ImagePullBackOff   0          23m
prometheus-adapter-6455646bdc-nwnsl   0/1     ImagePullBackOff   0          23m
prometheus-k8s-0                      2/2     Running            0          22m
prometheus-k8s-1                      2/2     Running            0          22m
prometheus-operator-f59c8b954-fvgxr   2/2     Running            0          23m

6、拉取失败的，修改镜像（根据失败镜像的名称，在kube-prometheus/manifests找对应的文件，以deployment.yaml结尾）

[root@master manifests]# vim kubeStateMetrics-deployment.yaml
       image: bitnami/kube-state-metrics:2.5.0

[root@master manifests]# kubectl apply -f kubeStateMetrics-deployment.yaml





[root@master manifests]# vim prometheusAdapter-deployment.yaml
       image: willdockerhub/prometheus-adapter:v0.9.1

[root@master manifests]# ：kubectl apply -f prometheusAdapter-deployment.yaml
[root@master manifests]# kubectl get pod  -n monitoring
NAME                                  READY   STATUS    RESTARTS   AGE
alertmanager-main-0                   2/2     Running   0          83m
alertmanager-main-1                   2/2     Running   0          83m
alertmanager-main-2                   2/2     Running   0          83m
blackbox-exporter-746c64fd88-dk4qt    3/3     Running   0          85m
grafana-5fc7f9f55d-n7szn              1/1     Running   0          85m
kube-state-metrics-6d7746678c-stq6g   3/3     Running   0          2m34s
node-exporter-h7f27                   2/2     Running   0          85m
node-exporter-j8lhq                   2/2     Running   0          85m
node-exporter-w65kk                   2/2     Running   0          85m
prometheus-adapter-c76fb84d7-6fq47    1/1     Running   0          60s
prometheus-adapter-c76fb84d7-dqs2k    0/1     Running   0          60s
prometheus-k8s-0                      2/2     Running   0          83m
prometheus-k8s-1                      2/2     Running   0          83m
prometheus-operator-f59c8b954-fvgxr   2/2     Running   0          85m

7、查看service（svc）

[root@master manifests]# kubectl get service -n monitoring
NAME                    TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
alertmanager-main       ClusterIP   10.97.204.202   <none>        9093/TCP,8080/TCP            93m
alertmanager-operated   ClusterIP   None            <none>        9093/TCP,9094/TCP,9094/UDP   92m
blackbox-exporter       ClusterIP   10.97.242.103   <none>        9115/TCP,19115/TCP           93m
grafana                 ClusterIP   10.100.15.208   <none>        3000/TCP                     93m
kube-state-metrics      ClusterIP   None            <none>        8443/TCP,9443/TCP            93m
node-exporter           ClusterIP   None            <none>        9100/TCP                     93m
prometheus-adapter      ClusterIP   10.107.77.167   <none>        443/TCP                      93m
prometheus-k8s          ClusterIP   10.96.2.27      <none>        9090/TCP,8080/TCP            93m
prometheus-operated     ClusterIP   None            <none>        9090/TCP                     92m
prometheus-operator     ClusterIP   None            <none>        8443/TCP                     93m

8、修改prometheus-service.yaml  ------ 在spec下，添加 type、nodePort

[root@master manifests]# vim prometheus-service.yaml

apiVersion: v1
kind: Service
metadata:
  labels:
    app.kubernetes.io/component: prometheus
    app.kubernetes.io/instance: k8s
    app.kubernetes.io/name: prometheus
    app.kubernetes.io/part-of: kube-prometheus
    app.kubernetes.io/version: 2.36.1
  name: prometheus-k8s
  namespace: monitoring
spec:
  type: NodePort         ### 添加type,注意格式与ports和selector同级
  ports:
  - name: web
    port: 9090
    targetPort: web
    nodePort: 30100      ### 指定端口，没有指定就自动生成
 #- name: reloader-web
 #  port: 8080
 #  targetPort: reloader-web
  selector:
    app.kubernetes.io/component: prometheus
    app.kubernetes.io/instance: k8s
    app.kubernetes.io/name: prometheus
    app.kubernetes.io/part-of: kube-prometheus
  sessionAffinity: ClientIP



[root@master manifests]# kubectl apply -f prometheus-service.yaml
service/prometheus-k8s configured

9、修改grafana-service.yaml ------ 在spec下，添加 type、nodePort

[root@master manifests]# vim grafana-service.yaml

apiVersion: v1
kind: Service
metadata:
  labels:
    app.kubernetes.io/component: grafana
    app.kubernetes.io/name: grafana
    app.kubernetes.io/part-of: kube-prometheus
    app.kubernetes.io/version: 8.5.5
  name: grafana
  namespace: monitoring
spec:
  type: NodePort         ### 添加type,注意格式与ports和selector同级
  ports:
  - name: http
    port: 3000
    targetPort: http
    nodePort: 30200      ### 指定端口，没有指定就自动生成
  selector:
    app.kubernetes.io/component: grafana
    app.kubernetes.io/name: grafana
    app.kubernetes.io/part-of: kube-prometheus



[root@master manifests]# kubectl apply -f grafana-service.yaml
service/grafana configured

10、修改alertmanager-service.yaml  ------ 在spec下，添加 type、nodePort

[root@master manifests]# vim alertmanager-service.yaml 


apiVersion: v1
kind: Service
metadata:
  labels:
    app.kubernetes.io/component: alert-router
    app.kubernetes.io/instance: main
    app.kubernetes.io/name: alertmanager
    app.kubernetes.io/part-of: kube-prometheus
    app.kubernetes.io/version: 0.24.0
  name: alertmanager-main
  namespace: monitoring
spec:
  type: NodePort   ### 添加type,注意格式与ports和selector同级
  ports:
  - name: web
    port: 9093
    targetPort: web
    nodePort: 30300    ### 指定端口，没有指定就自动生成
# - name: reloader-web
#   port: 8080
#   targetPort: reloader-web
  selector:
    app.kubernetes.io/component: alert-router
    app.kubernetes.io/instance: main
    app.kubernetes.io/name: alertmanager
    app.kubernetes.io/part-of: kube-prometheus
  sessionAffinity: ClientIP

[root@master manifests]# kubectl apply -f alertmanager-service.yaml 
service/alertmanager-main configured

11、再次查看service，出现外部访问的端口了

[root@master manifests]# kubectl get service -n monitoring
NAME                    TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                         AGE
alertmanager-main       NodePort    10.97.204.202   <none>        9093:30300/TCP,8080:31672/TCP   117m
alertmanager-operated   ClusterIP   None            <none>        9093/TCP,9094/TCP,9094/UDP      116m
blackbox-exporter       ClusterIP   10.97.242.103   <none>        9115/TCP,19115/TCP              117m
grafana                 NodePort    10.100.15.208   <none>        3000:30200/TCP                  117m
kube-state-metrics      ClusterIP   None            <none>        8443/TCP,9443/TCP               117m
node-exporter           ClusterIP   None            <none>        9100/TCP                        117m
prometheus-adapter      ClusterIP   10.107.77.167   <none>        443/TCP                         117m
prometheus-k8s          NodePort    10.96.2.27      <none>        9090:30100/TCP,8080:30543/TCP   117m
prometheus-operated     ClusterIP   None            <none>        9090/TCP                        116m
prometheus-operator     ClusterIP   None            <none>        8443/TCP                        117m

12、访问，使用集群的地址（192.168.2.x：30100/30200/30300）

[root@master manifests]# kubectl get nodes -o wide
NAME     STATUS   ROLES                  AGE   VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE                KERNEL-VERSION           CONTAINER-RUNTIME
master   Ready    control-plane,master   34d   v1.23.6   192.168.2.6   <none>        CentOS Linux 7 (Core)   3.10.0-1160.el7.x86_64   docker://20.10.17
node1   Ready    <none>                 34d   v1.23.6   192.168.2.3   <none>        CentOS Linux 7 (Core)   3.10.0-1160.el7.x86_64   docker://20.10.17
node2   Ready    <none>                 34d   v1.23.6   192.168.2.7   <none>        CentOS Linux 7 (Core)   3.10.0-1160.el7.x86_64   docker://20.10.17

13、grafana首次登陆用户和密码

admin

admin

SYHbb11
关注
K8S部署Prometheus
mcl914的博客
03-15 2796
前言：zabbix与prometheus的区别 和Zabbix类似，Prometheus也是一个近年比较火的开源监控框架，和Zabbix不同之处在于Prometheus相对更灵活点，模块间比较解耦，比如告警模块、代理模块等等都可以选择性配置。服务端和客户端都是开箱即用，不需要进行安装。zabbix则是一套安装把所有东西都弄好，很庞大也很繁杂。 zabbix的客户端agent可以比较方便的通过脚...
kubernetes部署prometheus
liuchao666888的博客
07-28 939
一、在k8s中部署prometheus 首先先下载prometheus镜像，不然部署时再下载会很慢 我这里用的是v2.2.1版本 [root@master ~]# docker pull prom/prometheus:v2.2.1 二、创建一个存储prometheus数据的目录 在你指定的prometheus节点中创建此目录，如果yanl文件中不配置指定节点，那每个节点都需要创建 [root@master ~]# mkdir /data [root@master ~]# chmod 777 /data
k8s快速搭建+prometheus部署及使用（纯干货！！！）
HoweWWW的博客
09-20 1618
MetalLB 为裸金属 Kubernetes 集群提供了一种实现 LoadBalancer 服务类型的有效方式，使得在没有云服务提供商支持的情况下，也能实现外部流量的负载均衡和高可用性。根据所有项目中的values.yaml中指定的image路径下载容器镜像并上传至harbor仓库。云平台会为我们分配vip并实现访问，如果是裸金属主机那么需要metallb来实现ip的分配。安装cri-docker插件（软件包安装）下载镜像上传至仓库，这里就直接使用了软件包。安装项目，在安装之前一定要上传镜像到仓库中。
运维开发实践 - Kubernetes - 部署Prometheus
Yuan_xii的博客
11-08 1001
prometheus部署
Kubernetes精讲之prometheus
m2282475145的博客
09-13 1318
Prometheus是一个开源的服务监控系统和时序数据库其提供了通用的数据模型和快捷数据采集、存储和查询接口它的核心组件Prometheus服务器定期从静态配置的监控目标或者基于服务发现自动配置的目标中进行拉取数据新拉取到啊的 数据大于配置的内存缓存区时，数据就会持久化到存储设备当中。
带你快速了解kubernetes部署prometheus监控prometheus-62.6.0.tar 
10-20
带你快速了解kubernetes部署prometheus监控prometheus-62.6.0.tar 
带你快速了解kubernetes部署prometheus监控kube-prometheus-stack-62.6.0.tgz
10-20
带你快速了解kubernetes部署prometheus监控kube-prometheus-stack-62.6.0.tgz
kubernetes部署prometheus监控nginx-exporter-1.3.0-debian-12-r2.tar
最新发布
10-20
kubernetes部署prometheus监控nginx-exporter-1.3.0-debian-12-r2.tar
带你快速了解kubernetes部署prometheus监控kube-state-metrics-2.13.0.tar
10-20
带你快速了解kubernetes部署prometheus监控kube-state-metrics-2.13.0.tar
Kubernetes中部署Prometheus监控平台
Andy12306的博客
08-01 173
这个YAML文件定义了一个名为"monitoring"的命名空间，并在该命名空间下创建了grafana-deploy、grafana-svc、metrics-server、node-exporter、prometheus-configmap、prometheus-deploy、prometheus-rbac和prometheus-svc的配置。Prometheus部署使用了Prometheus官方提供的镜像，并将Prometheus的Web界面暴露在9090端口。
Kubernetes 部署 Prometheus 监控系统
热门推荐
IT
01-02 1万+
Prometheus（普罗米修斯）是一个最初在SoundCloud上构建的开源监控报警系统和时序列数据库(TSDB).。自2012年成立以来，许多公司和组织都采用了Prometheus，该项目拥有一个非常活跃的开发人员和用户社区。它现在是一个独立的开源项目，可以独立于任何公司进行维护。为了强调这一点，并澄清项目的治理结构，Prometheus 于2016年加入 云计算本地计算基金会，作为继Kubernetes之后的第二个托管项目。............
Kubernetes 集群部署 Prometheus 和 Grafana
weixin_62922268的博客
08-20 1174
登录到 浏览器访问 http://192.168.80.11:30066/#/alerts ，登陆 alertmanager 即可看到。#通过上面可以看到 service 在 node 节点上映射的端口是 31000，这样我们访问 k8s 集群的 node 节点的 ip:31000，就可以访问到 prometheus 的 web ui 界面了。浏览器访问 http://192.168.80.11:31000 ，点击页面的 Status->Targets，查看 prometheus 的 targets。
Kubernetes实战prometheus部署
zhangkangren的博客
04-20 900
​ 本文介绍Prometheus 监控及在k8s集群中使用node-exporter、prometheus、grafana对集群进行监控。实现原理类似ELK、EFK组合。node-exporter组件负责收集节点上的metrics监控数据，并将数据推送给prometheus, prometheus负责存储这些数据，grafana将这些数据通过网页以图形的形式展现给用户。现在我们正式开始部署工作。这里假设你已经为你的K8S集群部署过kube-dns或者coredns了。
kubernets部署prometheus监控
weixin_68256171的博客
09-22 702
Prometheus是一个开源的服务监控系统和时序数据库其提供了通用的数据模型和快捷数据采集、存储和查询接口它的核心组件Prometheus服务器定期从静态配置的监控目标或者基于服务发现自动配置的目标中进行拉取数据新拉取到的数据大于配置的内存缓存区时，数据就会持久化到存储设备当中。
Kubernetes基础自学系列 | 部署prometheus
COCO_gsta的博客
04-11 905
视频来源：B站《2021 年末倾力打造 Kubernetes 入门至精通 - 2022 年幸福的开胃菜》 一边学习一边整理老师的课程内容及试验笔记，并与大家分享，侵权即删，谢谢支持！ 附上汇总贴：Kubernetes基础自学系列 | 汇总_COCOgsta的博客-CSDN博客 Operator 是何物 Kubernetes Operator 是一种封装、部署和管理 Kubernetes 应用的方法。我们使用 Kubernetes API（应用编程接口）和 kubectl 工具在 Kubernetes
Kubernetes（k8s）部署Promehteus（kube-prometheus&kube-prometheus-stack）监控
匠人精神，持之以恒！
10-24 2377
文章目录一、概述1）metrics-server简介2）Prometheus简介3）metrics-server&Promehteus对比&特性二、使用Helm安装kube-prometheus-stack及其它组件1）安装Prometheus 一、概述 在1.8版本以后heapster由metrics-server替代；从k8s的v1.11版本开始已经全面转向以Prometheus为核心的新监控体系架构 1）metrics-server简介 metrics-server 通过kube
kubernetes部署Prometheus
weixin_67405599的博客
11-03 845
k8s中运行Prometheus
10-4 Kubernetes 部署 prometheus
qq_25775675的博客
12-20 963
一、下载地址 Prometheus github 地址：https://github.com/coreos/kube-prometheus 二、组件说明 1.MetricServer：是kubernetes集群资源使用情况的聚合器，收集数据给kubernetes集群内使用，如kubectl,hpa,scheduler等。 2.PrometheusOperator：是一个系统监测和警报工具箱，用来存储监控数据。 3.NodeExporter：用于各node的关键度量指标状态数据。 4.KubeStateMet
Kubernetes环境部署Prometheus和Grafana监控系统指南
资源摘要信息:"Kubernetes部署监控系统Prometheus和Grafana(亲测可用)" 知识点一：Kubernetes简介 Kubernetes是一个开源的容器编排平台，...以上就是通过Kubernetes部署Prometheus和Grafana的基本步骤和相关知识点。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值