Kube-prometheus Deploy Prometheus

Kube-prometheus Deploy Prometheus

部署 Prometheus

下载 Kube-prometheus

wget -c https://github.com/prometheus-operator/kube-prometheus/archive/refs/tags/v0.11.0.tar.gz

查看镜像

grep -rn 'image: '

examples/example-app/example-app.yaml:36:        image: quay.io/fabxc/prometheus_demo_service
examples/thanos-sidecar.jsonnet:11:          image: 'quay.io/thanos/thanos:v0.19.0',
experimental/metrics-server/metrics-server-deployment.yaml:21:        image: gcr.io/google_containers/metrics-server-amd64:v0.2.0

manifests/alertmanager-alertmanager.yaml:13:  image: quay.io/prometheus/alertmanager:v0.24.0
manifests/blackboxExporter-deployment.yaml:33:        image: quay.io/prometheus/blackbox-exporter:v0.21.0
manifests/blackboxExporter-deployment.yaml:60:        image: jimmidyson/configmap-reload:v0.5.0
manifests/blackboxExporter-deployment.yaml:88:        image: quay.io/brancz/kube-rbac-proxy:v0.12.0
manifests/grafana-deployment.yaml:33:        image: grafana/grafana:8.5.5
manifests/kubeStateMetrics-deployment.yaml:35:        image: k8s.gcr.io/kube-state-metrics/kube-state-metrics:v2.5.0
manifests/kubeStateMetrics-deployment.yaml:56:        image: quay.io/brancz/kube-rbac-proxy:v0.12.0
manifests/kubeStateMetrics-deployment.yaml:82:        image: quay.io/brancz/kube-rbac-proxy:v0.12.0
manifests/nodeExporter-daemonset.yaml:38:        image: quay.io/prometheus/node-exporter:v1.3.1
manifests/nodeExporter-daemonset.yaml:74:        image: quay.io/brancz/kube-rbac-proxy:v0.12.0
manifests/prometheus-prometheus.yaml:21:  image: quay.io/prometheus/prometheus:v2.36.1
manifests/prometheusAdapter-deployment.yaml:40:        image: k8s.gcr.io/prometheus-adapter/prometheus-adapter:v0.9.1
manifests/prometheusOperator-deployment.yaml:33:        image: quay.io/prometheus-operator/prometheus-operator:v0.57.0
manifests/prometheusOperator-deployment.yaml:56:        image: quay.io/brancz/kube-rbac-proxy:v0.12.0

镜像 tag 重置及推送镜像到 harbor

# docker pull gcr.io/google_containers/metrics-server-amd64:v0.2.0
# Error response from daemon: Get "https://gcr.io/v2/": dial tcp 74.125.203.82:443: connect: connection timed out
# 使用阿里云仓库
docker pull registry.aliyuncs.com/google_containers/metrics-server-amd64:v0.2.0

docker pull quay.io/prometheus/alertmanager:v0.24.0
docker pull quay.io/prometheus/blackbox-exporter:v0.21.0
docker pull jimmidyson/configmap-reload:v0.5.0
docker pull quay.io/brancz/kube-rbac-proxy:v0.12.0
docker pull grafana/grafana:8.5.5

# docker pull k8s.gcr.io/kube-state-metrics/kube-state-metrics:v2.5.0
# 使用阿里云仓库
# docker pull registry.cn-hangzhou.aliyuncs.com/google_containers/kube-state-metrics/kube-state-metrics:v2.5.0
# docker pull registry.aliyuncs.com/google_containers/kube-state-metrics/kube-state-metrics:v2.5.0
# dockerhub 拉取
docker pull landv1001/kube-state-metrics:v2.5.0

docker pull quay.io/brancz/kube-rbac-proxy:v0.12.0
docker pull quay.io/brancz/kube-rbac-proxy:v0.12.0
docker pull quay.io/prometheus/node-exporter:v1.3.1
docker pull quay.io/brancz/kube-rbac-proxy:v0.12.0
docker pull quay.io/prometheus/prometheus:v2.36.1

# docker pull k8s.gcr.io/prometheus-adapter/prometheus-adapter:v0.9.1
# 使用阿里云仓库
# docker pull registry.aliyuncs.com/google_containers/prometheus-adapter/prometheus-adapter:v0.9.1
# dockerhub 拉取
docker pull v5cn/prometheus-adapter:v0.9.1

docker pull quay.io/prometheus-operator/prometheus-operator:v0.57.0
docker pull quay.io/brancz/kube-rbac-proxy:v0.12.0

docker tag registry.aliyuncs.com/google_containers/metrics-server-amd64:v0.2.0  10.83.195.8:1443/prometheus/metrics-server-amd64:v0.2.0
docker tag quay.io/prometheus/alertmanager:v0.24.0 10.83.195.8:1443/prometheus/alertmanager:v0.24.0
docker tag quay.io/prometheus/blackbox-exporter:v0.21.0 10.83.195.8:1443/prometheus/blackbox-exporter:v0.21.0
docker tag jimmidyson/configmap-reload:v0.5.0 10.83.195.8:1443/prometheus/configmap-reload:v0.5.0
docker tag quay.io/brancz/kube-rbac-proxy:v0.12.0 10.83.195.8:1443/prometheus/kube-rbac-proxy:v0.12.0
docker tag grafana/grafana:8.5.5 10.83.195.8:1443/prometheus/grafana:8.5.5
docker tag landv1001/kube-state-metrics:v2.5.0 10.83.195.8:1443/prometheus/kube-state-metrics:v2.5.0
docker tag quay.io/prometheus/node-exporter:v1.3.1 10.83.195.8:1443/prometheus/node-exporter:v1.3.1
docker tag quay.io/prometheus/prometheus:v2.36.1 10.83.195.8:1443/prometheus/prometheus:v2.36.1
docker tag v5cn/prometheus-adapter:v0.9.1 10.83.195.8:1443/prometheus/prometheus-adapter:v0.9.1
docker tag quay.io/prometheus-operator/prometheus-operator:v0.57.0 10.83.195.8:1443/prometheus/prometheus-operator:v0.57.0

docker push 10.83.195.8:1443/prometheus/metrics-server-amd64:v0.2.0
docker push 10.83.195.8:1443/prometheus/alertmanager:v0.24.0
docker push 10.83.195.8:1443/prometheus/blackbox-exporter:v0.21.0
docker push 10.83.195.8:1443/prometheus/configmap-reload:v0.5.0
docker push 10.83.195.8:1443/prometheus/kube-rbac-proxy:v0.12.0
docker push 10.83.195.8:1443/prometheus/grafana:8.5.5
docker push 10.83.195.8:1443/prometheus/kube-state-metrics:v2.5.0
docker push 10.83.195.8:1443/prometheus/node-exporter:v1.3.1
docker push 10.83.195.8:1443/prometheus/prometheus:v2.36.1
docker push 10.83.195.8:1443/prometheus/prometheus-adapter:v0.9.1
docker push 10.83.195.8:1443/prometheus/prometheus-operator:v0.57.0

docker pull bitnami/pushgateway:1.8.0
docker tag bitnami/pushgateway:1.8.0 10.83.195.8:1443/prometheus/pushgateway:1.8.0
docker push 10.83.195.8:1443/prometheus/pushgateway:1.8.0

docker pull quay.io/prometheus-operator/prometheus-config-reloader:v0.57.0
do
### 可能原因分析 #### 1. 命名空间配置错误 如果在部署过程中未指定正确的命名空间,则可能导致资源被创建到其他命名空间而非默认的 `default` 命名空间中。例如,在执行 Helm 安装命令时,如果没有显式指定 `-n kube-prometheus` 参数,默认情况下会尝试将资源部署到 `default` 命名空间[^1]。然而,由于某些配置文件中的设置(如 `values.yaml`),实际可能选择了不同的命名空间。 ```bash helm upgrade -i kube-prometheus-stack -f values.yaml . -n kube-prometheus ``` 此命令明确指定了 `-n kube-prometheus`,因此即使用户期望看到的是 `default` 中的内容,实际上所有的资源都被放置到了名为 `kube-prometheus` 的命名空间下[^1]。 #### 2. 配置文件问题 (`values.yaml`) Helm Chart 的行为很大程度依赖于传递给它的自定义参数或覆盖值。假如提供的 `values.yaml` 文件存在语法错误或者逻辑冲突,可能会阻止正常安装过程完成并留下部分未初始化的状态。比如 Prometheus Server 或 AlertManager Pod 处于 CrashLoopBackOff 状态可能是由无效数据源路径引起[^2]: ```yaml serverFiles: prometheus.yml: | scrape_configs: - job_name: 'kubernetes-nodes' static_configs: - targets: ['localhost:9090'] ``` 这里展示了一个简单的例子来调整抓取目标列表;但如果类似的字段拼写失误则容易引发异常终止。 #### 3. 权限不足或其他集群环境因素 Kubernetes API 访问权限不足也会阻碍服务账户绑定成功从而影响整个应用栈启动。另外还有网络插件兼容性、存储类预设等问题都需逐一排查确认是否存在干扰项[^3]: - **ServiceAccount & RoleBinding**: 检查是否有足够的 RBAC 授权允许访问所需节点指标端口。 - **Network Policies**: 如果启用了严格的流量控制策略,确保不会误拦内部通信请求。 - **Persistent Volumes (PV)** 和 Persistent Volume Claims(PVC): 对持久化需求较高的组件来说,缺少合适的磁盘分区分配方案同样会造成挂载失败现象。 --- ### 解决方法建议 针对以上提到的各种可能性可以采取如下措施逐步定位具体症结所在: 1. 使用 `helm status <release-name>` 获取更详细的当前版本信息以便了解确切发生了什么状况; ```bash helm status kube-prometheus-stack --namespace=kube-prometheus ``` 2. 察看日志记录寻找潜在提示消息 ```bash kubectl logs deploy/<component> -n kube-prometheus ``` 3. 核实所使用的镜像标签号是否匹配官方文档推荐的标准组合形式; 4. 尝试重新运行原始指令前先清理残留对象再重头开始验证流程顺畅度如何变化。 最后记得备份好重要资料后再做任何大规模改动操作!
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值