In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-03-29 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >
Share
Shulou(Shulou.com)06/01 Report--
This article mainly explains "how to solve the problem of installing heapster error". The explanation content in this article is simple and clear, easy to learn and understand. Please follow the idea of Xiaobian and go deep into it slowly to study and learn "how to solve the problem of installing heapster error" together.
Error message:
I0302 06:10:25.009896 1 influxdb.go:274] Created database "k8s" on influxDB server at "monitoring-influxdb.kube-system.svc:8086"
E0302 06:11:05.004391 1 manager.go:101] Error in scraping containers from kubelet:172.16.8.12:10255: failed to get all container stats from Kubelet URL
"http://172.16.8.12:10255/stats/container/": Post http://172.16.8.12:10255/stats/container/: dial tcp 172.16.8.12:10255: getsockopt: connection refused
E0302 06:11:05.006654 1 manager.go:101] Error in scraping containers from kubelet:172.16.8.13:10255: failed to get all container stats from Kubelet URL
"http://172.16.8.13:10255/stats/container/": Post http://172.16.8.13:10255/stats/container/: dial tcp 172.16.8.13:10255: getsockopt: connection refused
E0302 06:11:05.024545 1 manager.go:101] Error in scraping containers from kubelet:172.16.8.14:10255: failed to get all container stats from Kubelet URL
"http://172.16.8.14:10255/stats/container/": Post http://172.16.8.14:10255/stats/container/: dial tcp 172.16.8.14:10255: getsockopt: connection refused
W0302 06:11:25.000741 1 manager.go:152] Failed to get all responses in time (got 0/3)
Solution:
[root@k8s1 ~]# vim 111.yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
annotations:
rbac.authorization.kubernetes.io/autoupdate: "true"
labels:
kubernetes.io/bootstrapping: rbac-defaults
name: system:heapster
rules:
- apiGroups:
- ""
resources:
- events
- namespaces
- nodes
- pods
- nodes/stats
verbs:
- create
- get
- list
- watch
- apiGroups:
- extensions
resources:
- deployments
verbs:
- get
- list
- watch
[root@k8s1 ~]# kubectl apply -f 111.yaml
Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply
clusterrole.rbac.authorization.k8s.io/system:heapster configured
[root@k8s1 ~]# kubectl delete -f heapster.yaml
serviceaccount "heapster" deleted
deployment.apps "heapster" deleted
service "heapster" deleted
[root@k8s1 ~]# kubectl apply -f heapster.yaml
serviceaccount/heapster created
deployment.apps/heapster created
service/heapster created
[root@k8s1 ~]#
Thank you for reading, the above is the "installation heapster error how to solve" the content, after the study of this article, I believe that we have a deeper understanding of how to install heapster error how to solve this problem, the specific use of the situation also needs to be verified by practice. Here is, Xiaobian will push more articles related to knowledge points for everyone, welcome to pay attention!
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.