一起来学k8s 34.二进制k8s集群安装prometheus-operator

最新推荐文章于 2024-07-15 13:40:26 发布
最新推荐文章于 2024-07-15 13:40:26 发布
阅读量1.5k 收藏 3
点赞数
分类专栏： kubernetes 文章标签： kubernets
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/tangwei0928/article/details/99711322
版权

二进制k8s集群安装prometheus-operator

环境准备

##/etc/hosts
192.168.48.101 master01
192.168.48.102 master02
192.168.48.103 master03
192.168.48.201 node01
192.168.48.202 node02
192.168.48.54  nfs

## keepalived的vip
192.168.48.66
IPHostnameCPUMemory
192.168.48.101master0124G
192.168.48.102master0224G
192.168.48.103master0324G
192.168.48.201node0124G
192.168.48.202node0224G
192.168.48.54nfs24G
软件版本
kubernetes1.15.2
docker-ce19.03
calico3.8
etcd3.3.13
CNI0.8.1
coredns1.4.0
metrics-server0.3.3
ingress-controller0.25.0
dashboard1.10.1
Weave Scope1.11.4
nfsv4
helm2.14.3
harbor1.1.1

安装

下载部署文件

https://github.com/coreos/kube-prometheus.git

下载地址
链接: https://pan.baidu.com/s/1uA4Lf3ZUfg0b1YLpoSRGHw 提取码: pw58

unzip kube-prometheus-0.2.0.zip

mkdir prometheus

cp kube-prometheus-0.2.0/manifests/* prometheus/

cd prometheus/

mkdir -p operator node-exporter alertmanager grafana kube-state-metrics prometheus serviceMonitor adapter

mv *-serviceMonitor* serviceMonitor/
mv 0prometheus-operator* operator/
mv grafana-* grafana/
mv kube-state-metrics-* kube-state-metrics/
mv alertmanager-* alertmanager/
mv node-exporter-* node-exporter/
mv prometheus-adapter* adapter/
mv prometheus-* prometheus/

[root@master01 prometheus]# pwd
/root/prometheus

[root@master01 prometheus]# ll
total 20
-rw-r--r-- 1 root root   60 Aug 18 21:01 00namespace-namespace.yaml
drwxr-xr-x 2 root root 4096 Aug 18 21:01 adapter
drwxr-xr-x 2 root root  149 Aug 18 21:01 alertmanager
drwxr-xr-x 2 root root  219 Aug 18 21:01 grafana
drwxr-xr-x 2 root root  305 Aug 18 21:01 kube-state-metrics
drwxr-xr-x 2 root root  200 Aug 18 21:01 node-exporter
drwxr-xr-x 2 root root 4096 Aug 18 21:01 operator
drwxr-xr-x 2 root root 4096 Aug 18 21:01 prometheus
drwxr-xr-x 2 root root 4096 Aug 18 21:01 serviceMonitor

查看node的label

[root@master01 prometheus]# curl -s https://zhangguanzhang.github.io/bash/label.sh | bash
Node                                    Label       
master01	
            app	ingress
            beta.kubernetes.io/arch	amd64
            beta.kubernetes.io/os	linux
            kubernetes.io/arch	amd64
            kubernetes.io/hostname	master01
            kubernetes.io/os	linux
            node-role.kubernetes.io/master	
master02	
            beta.kubernetes.io/arch	amd64
            beta.kubernetes.io/os	linux
            kubernetes.io/arch	amd64
            kubernetes.io/hostname	master02
            kubernetes.io/os	linux
            node-role.kubernetes.io/master	
master03	
            beta.kubernetes.io/arch	amd64
            beta.kubernetes.io/os	linux
            kubernetes.io/arch	amd64
            kubernetes.io/hostname	master03
            kubernetes.io/os	linux
            node-role.kubernetes.io/master	
node01	
            beta.kubernetes.io/arch	amd64
            beta.kubernetes.io/os	linux
            kubernetes.io/arch	amd64
            kubernetes.io/hostname	node01
            kubernetes.io/os	linux
            node-role.kubernetes.io/node	
node02	
            beta.kubernetes.io/arch	amd64
            beta.kubernetes.io/os	linux
            kubernetes.io/arch	amd64
            kubernetes.io/hostname	node02
            kubernetes.io/os	linux
            node-role.kubernetes.io/node

查看是否匹配prometheus里的label

[root@master01 prometheus]# grep -A1 nodeSelector alertmanager/alertmanager-alertmanager.yaml
  nodeSelector:
    kubernetes.io/os: linux

镜像下载

quay.io/prometheus/node-exporter:v0.18.1
quay.io/prometheus/alertmanager:v0.18.0
quay.io/prometheus/prometheus:v2.11.0
quay.io/coreos/configmap-reload:v0.0.1
quay.io/coreos/prometheus-config-reloader:v0.33.0
quay.io/coreos/prometheus-operator:v0.33.0
quay.io/coreos/kube-rbac-proxy:v0.4.1
quay.io/coreos/kube-state-metrics:v1.7.2
quay.io/coreos/k8s-prometheus-adapter-amd64:v0.4.1
k8s.gcr.io/addon-resizer:1.8.4
grafana/grafana:6.2.2

链接: https://pan.baidu.com/s/19tUbs8bBQYDrLeHNcKXv-Q 提取码: qs7t

docker load -i prom.tar.gz

部署namespace

[root@master01 prometheus]# kubectl apply -f 00namespace-namespace.yaml 
namespace/monitoring created

部署operator

[root@master01 prometheus]# kubectl apply -f operator/
customresourcedefinition.apiextensions.k8s.io/alertmanagers.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/podmonitors.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/prometheuses.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/prometheusrules.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/servicemonitors.monitoring.coreos.com created
clusterrole.rbac.authorization.k8s.io/prometheus-operator created
clusterrolebinding.rbac.authorization.k8s.io/prometheus-operator created
deployment.apps/prometheus-operator created
service/prometheus-operator created
serviceaccount/prometheus-operator created

[root@master01 prometheus]# kubectl -n monitoring get pod
NAME                                   READY   STATUS    RESTARTS   AGE
prometheus-operator-7447bf4dcb-qw4jn   1/1     Running   0          27s

部署整套CRD

kubectl apply -f adapter/
kubectl apply -f alertmanager/
kubectl apply -f node-exporter/
kubectl apply -f kube-state-metrics/
kubectl apply -f grafana/
kubectl apply -f prometheus/
kubectl apply -f serviceMonitor/

查看整体部署情况

[root@master01 prometheus]# kubectl -n monitoring get all
NAME                                       READY   STATUS    RESTARTS   AGE
pod/alertmanager-main-0                    2/2     Running   0          88s
pod/alertmanager-main-1                    2/2     Running   0          63s
pod/alertmanager-main-2                    2/2     Running   0          47s
pod/grafana-7dc5f8f9f6-n7vws               1/1     Running   0          73s
pod/kube-state-metrics-59c47cfcfb-q9255    4/4     Running   0          62s
pod/node-exporter-2psjp                    2/2     Running   0          87s
pod/node-exporter-7tcsb                    2/2     Running   0          87s
pod/node-exporter-hm8g8                    2/2     Running   0          87s
pod/node-exporter-mccdw                    2/2     Running   0          87s
pod/node-exporter-xtxc2                    2/2     Running   0          87s
pod/prometheus-adapter-668748ddbd-nwmxl    1/1     Running   0          89s
pod/prometheus-k8s-0                       3/3     Running   0          72s
pod/prometheus-k8s-1                       3/3     Running   1          72s
pod/prometheus-operator-7447bf4dcb-qw4jn   1/1     Running   0          2m35s


NAME                            TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)             AGE
service/alertmanager-main       ClusterIP   10.103.101.118   <none>        9093/TCP            89s
service/alertmanager-operated   ClusterIP   None             <none>        9093/TCP,6783/TCP   89s
service/grafana                 ClusterIP   10.102.56.50     <none>        3000/TCP            74s
service/kube-state-metrics      ClusterIP   None             <none>        8443/TCP,9443/TCP   87s
service/node-exporter           ClusterIP   None             <none>        9100/TCP            88s
service/prometheus-adapter      ClusterIP   10.97.209.217    <none>        443/TCP             90s
service/prometheus-k8s          ClusterIP   10.107.103.78    <none>        9090/TCP            72s
service/prometheus-operated     ClusterIP   None             <none>        9090/TCP            72s
service/prometheus-operator     ClusterIP   None             <none>        8080/TCP            2m36s

NAME                           DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
daemonset.apps/node-exporter   5         5         5       5            5           kubernetes.io/os=linux   88s

NAME                                  READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/grafana               1/1     1            1           74s
deployment.apps/kube-state-metrics    1/1     1            1           88s
deployment.apps/prometheus-adapter    1/1     1            1           90s
deployment.apps/prometheus-operator   1/1     1            1           2m36s

NAME                                             DESIRED   CURRENT   READY   AGE
replicaset.apps/grafana-7dc5f8f9f6               1         1         1       74s
replicaset.apps/kube-state-metrics-59c47cfcfb    1         1         1       62s
replicaset.apps/kube-state-metrics-77467ddf9b    0         0         0       88s
replicaset.apps/prometheus-adapter-668748ddbd    1         1         1       90s
replicaset.apps/prometheus-operator-7447bf4dcb   1         1         1       2m36s

NAME                                 READY   AGE
statefulset.apps/alertmanager-main   3/3     89s
statefulset.apps/prometheus-k8s      2/2     72s

创建ingress

[root@master01 prometheus]# kubectl get svc -n monitoring 
NAME                    TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)             AGE
alertmanager-main       ClusterIP   10.103.101.118   <none>        9093/TCP            6m22s
alertmanager-operated   ClusterIP   None             <none>        9093/TCP,6783/TCP   6m22s
grafana                 ClusterIP   10.102.56.50     <none>        3000/TCP            6m7s
kube-state-metrics      ClusterIP   None             <none>        8443/TCP,9443/TCP   6m20s
node-exporter           ClusterIP   None             <none>        9100/TCP            6m21s
prometheus-adapter      ClusterIP   10.97.209.217    <none>        443/TCP             6m23s
prometheus-k8s          ClusterIP   10.107.103.78    <none>        9090/TCP            6m5s
prometheus-operated     ClusterIP   None             <none>        9090/TCP            6m5s
prometheus-operator     ClusterIP   None             <none>        8080/TCP            7m29s


vim prometheus-ingress.yaml

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: prometheus.com
  namespace: monitoring
  annotations:
    kubernetes.io/ingress.class: "nginx"
spec:
  rules:
  - host: grafana.tk8s.com
    http:
      paths:
      - backend:
          serviceName: grafana
          servicePort: 3000
  - host: prometheus.tk8s.com
    http:
      paths:
      - backend:
          serviceName: prometheus-k8s
          servicePort: 9090
  - host: alertmanager.tk8s.com
    http:
      paths:
      - backend:
          serviceName: alertmanager-main
          servicePort: 9093

[root@master01 prometheus]# kubectl apply -f prometheus-ingress.yaml 
ingress.extensions/prometheus.com created

访问prometheus

在这里插入图片描述

在这里插入图片描述

在这里插入图片描述

所有master修改systemd配置文件，修改bind

vim /usr/lib/systemd/system/kube-controller-manager.service

....
--bind-address=0.0.0.0 \

systemctl daemon-reload 
systemctl restart kube-controller-manager.service 

vim /usr/lib/systemd/system/kube-scheduler.service
....
--address=0.0.0.0 \

systemctl daemon-reload 
systemctl restart systemctl restart kube-scheduler.service

创建kube-controller-manager和kube-scheduler的svc

vim prom-svc.yaml

apiVersion: v1
kind: Service
metadata:
  namespace: kube-system
  name: kube-controller-manager
  labels:
    k8s-app: kube-controller-manager
spec:
  type: ClusterIP
  clusterIP: None
  ports:
  - name: http-metrics
    port: 10252
    targetPort: 10252
    protocol: TCP
---
apiVersion: v1
kind: Service
metadata:
  namespace: kube-system
  name: kube-scheduler
  labels:
    k8s-app: kube-scheduler
spec:
  type: ClusterIP
  clusterIP: None
  ports:
  - name: http-metrics
    port: 10251
    targetPort: 10251
    protocol: TCP

---
apiVersion: v1
kind: Endpoints
metadata:
  labels:
    k8s-app: kube-controller-manager
  name: kube-controller-manager
  namespace: kube-system
subsets:
- addresses:
  - ip: 192.168.48.101
  - ip: 192.168.48.102
  - ip: 192.168.48.103
  ports:
  - name: http-metrics
    port: 10252
    protocol: TCP

---
apiVersion: v1
kind: Endpoints
metadata:
  labels:
    k8s-app: kube-scheduler
  name: kube-scheduler
  namespace: kube-system
subsets:
- addresses:
  - ip: 192.168.48.101
  - ip: 192.168.48.102
  - ip: 192.168.48.103
  ports:
  - name: http-metrics
    port: 10251
    protocol: TCP

[root@master01 prometheus]# kubectl apply -f prom-svc.yaml

在这里插入图片描述

访问grafana

grafana初始用户名和密码都是是admin

在这里插入图片描述

在这里插入图片描述

隔壁小翔
关注
  • 0
    点赞
  • 踩
  • 3
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
K8S二进制部署详解，一文教会你部署高可用K8S集群
景天科技苑
02-07 4045
虽然kubeadm方式搭建K8S比较简单，但是对里面的原理都不清楚的话，生产中使用功能可能不便于排查故障。二进制方式部署的k8s集群比较稳定。 二进制方式搭建：在官网下载相关组件的二进制包，如果手动安装，对kubernetes理解也会更全面。 Kubeadm和二进制都适合生产环境，在生产环境运行都很稳定，具体如何选择，可以根据实际项目进行评估。
8-1 基于Operator和二进制安装Prometheus系统
分享云原生，容器，运维等干货知识
10-11 513
Prometheus是一个开源系统监控和警报工具包，最初由SoundCloud构建。自2012年推出以来，许多公司和组织都采用了Prometheus，该项目拥有非常活跃的开发人员和用户社区。现在它是一个独立的开源项目，独立于任何公司进行维护。为了强调这一点，也为了明确项目的治理结构，Prometheus在2016年加入了云原生计算基金会，成为继Kubernetes之后的第二个托管项目。
kube-prometheus 介绍和安装讲解（k8s环境推荐）
weixin_44093727的博客
02-11 1741
介绍了kube-prometheus 介绍和安装讲解（k8s环境推荐）
k8s安装Prometheus+Grafana
zhangshaohuas的博客
08-07 1897
环境 centos7 k8s部署方式 kubeadm k8s版本号 v1.17.0 前提条件： 部署nfs服务 目录权限必须是777 [root@k8s-node1 data]# cat /etc/exports /nfs 192.168.1.0/24(rw) 目录结构：（最终） [root@k8s-node1 nfs]# tree . ├── grafana │ └── data │ └── prometheus └── data [...
prometheus operator
最新发布
qq_31055683的博客
07-15 1128
Prometheus 开源的系统监控和报警框架，本身也是一个时序数据库（TSDB）
k8s集成kube-prometheus
谭宇
01-30 523
正文 下载kube-prometheus，注意与k8s版本对应支持，k8s-1.25版本使用kube-prometheus-release-0.12 克隆仓库，按照指引使用kubectl安装prometheus git clone -b release-0.12 https://github.com/prometheus-operator/kube-prometheus.git cd kube-p...
k8s安装kube-promethues（超详细）
阿甘兄
05-23 3092
文章目录01 引言02 kube-prometheus安装2.1 step1：分类yaml2.2 step2：修改数据持久化存储2.2.1 修改Prometheus 持久化2.2.2 修改grafana持久化配置2.3 step3：修改 Service 端口设置2.3.1 修改 Prometheus Service2.3.2 修改 Grafana Service2.4 step4：安装promethues-operator2.5 step5：验证03 文末 01 引言 本文主要讲解在k8s（kuberne
kube-promethesu新增k8s组件监控（etcd\kube-controller-manage\kube-scheduler）
jingleli21的博客
06-05 1142
Kube-prometheus默认是配置了kube-controller-manager的servicemonitor的，但是因为我们是二进制部署的，所以无法找到对应的kube-contorller-manager的service和endpoints,所以这里我们需要自己去手动创建service和endpoints。备注：看到不少的资料都是说需要修改kube-controller-manager和kube-scheduler的监听地址，从127.0.0.1修改成0.0.0.0。
prometheus-operator监控kubernetes集群及二进制k8s组件
ai418348851的博客
04-22 879
环境 kubernetes: v1.17.3 kube-prometheus 部署 获取源码 需要安装git yum -y install git 下载官方prometheus-operator git clone https://github.com/coreos/kube-prometheus.git ## 或使用我自己的github文件省去下面所有配置直接kubectl apply -f...
k8s Helm安装Prometheus Operator
dz45693的专栏
08-29 3444
Ubuntu 18 Kubernetes集群的安装和部署 以及Helm的安装完成了k8s的集群和helm的安装，今天我们来看看Prometheus的监控怎么搞。Prometheus Operator 是 CoreOS 开发的基于 Prometheus 的 Kubernete s监控方案，也可能是目前功能最全面的开源方案。更多信息可以查看https://github.com/coreos/prom...
离线部署K8S集群(二进制方式)
烟花散尽不问繁华
05-07 1561
一、前置准备 准备三台服务器，操作系统centos7.x 硬件配置：CPU2核、内存2GB、硬盘30GB 确保机器间网络互通，时钟同步，所需镜像及资源包下载链接：点击下载 规划： 节点名称 IP 安装组件 k8s-master 192.168.14.101 docker、etcd、kubelet、kube-proxy、kube-apiserver、kube-controller-manager、kube-scheduler k8s-node1 192.168.14.102 docker、
二进制安装k8s
nsydgs的博客
07-29 1356
Kubernetes概述
Prometheus Operator（三） 监控ETCD集群
qq_23435961的博客
12-11 1009
Prometheus Operator 监控ETCD集群 现在我们需要自定义Prometheus operator，这里以监控ETCD为例。由于我们的etcd是跑在kubernetes外部的，想要监控到， 除了prometheus operator自带的资源对象，节点以及组件监控，有的时候实际的业务场景需要我们自定义监控项 确保有metric数据 创建ServiceMonitor对象，用于添加Prometheus添加监控项 ServiceMonitor关联metrics数据接口的一个Service对象 确
基于Kube-Prometheus/v0.13.0的K8S监控部署
u010100623的博客
07-05 1031
有时候我们可能需要添加集群外部的一些监控，比如MySQL、Redis、Kafka等，我们可以新建一个 prometheus-additional.yaml 文件，配置scrape_configs来添加额外监控组件。（1）添加prometheus-additional.yaml文件，假设我们要添加MySQL和Redis的监控- targets:- targets:（2）然后我们需要将这些监控配置以secret资源类型存储到k8s集群中。
ocp3.11部署prometheus-operator:v0.34.0，并使用prometheus-adapter做hpa
Yu的博客
04-26 477
环境 ocp3.11 prometheus-operator 安装ocp3.11的时候会默认安装与3.11匹配的prometheus-operator。我想使用prometheus-operator的remote write功能，但是这个默认安装的prometheus-operator不支持。 于是就开始折腾把k8s中的prometheus-operator v0.34.0给安装到ocp3.11中。 大部分yaml文件都是可以直接跑的，只有小部分yaml需要手动调整。 需要调整的yaml 说明
kubernetes v1.20.6部署kube-prometheus
Vic的博客
08-10 451
下载 github地址 https://github.com/prometheus-operator/kube-prometheus wget https://github.com/prometheus-operator/kube-prometheus/archive/refs/tags/v0.8.0.tar.gz tar -zxf kube-prometheus-0.8.0.tar.gz cd kube-prometheus-0.8.0/manifests 所有配置均在manifest
prometheus之K8S-完整篇
weixin_42562106的博客
02-12 1119
cat <<END>prometheus.yaml apiVersion: v1 kind: ServiceAccount metadata: labels: component: "server" app: prometheus release: prometheus chart: prometheus-11.16.2 heritage: Helm name: prometheus namespace: istio-system a
关于k8s中部署kubesphere的prometheus-k8s-0容器报CrashLoopBackoff问题
weixin_43804233的博客
06-18 197
查阅大量资料，包括问gpt都无济于事，说是和内存相关，但是无法定位到具体的问题点，后面通过官方论坛和群，寻求帮助后给了一个排除的思路从而解决；判定是和nfs存储不兼容，我是arm架构的，网上说amd可正常使用。所以我现在改用的是本机存储。重新apply一下就正常了。
k8s部署kube-prometheus
MssGuo的博客
10-21 2799
k8s部署kube-prometheus
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值