Metric server unable to fetch monitoring data from the node where his pod is placed
up vote
0
down vote
favorite
I am trying to figure out why Metric server isn't collecting stats from the node where it is deployed (r2s13). There are 3 nodes in my cluster (1 master and 2 workers).
metric server version: 0.3.1
kubernetes version: 1.12 (installed with kubeadm)
CNI plugin: weave net
kubectl top node output:
NAME CPU(cores) CPU% MEMORY(bytes) MEMORY%
r2s12 344m 4% 3079Mi 12%
r2s14 67m 0% 1695Mi 21%
r2s13
In metric server log, I have the below line repeated (just for the node where the metric server is deployed r2s13):
E1023 15:28:14.643011 1 manager.go:102] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:r2s13: unable to fetch metrics from Kubelet r2s13 (10.199.183.218): Get https://10.199.183.218:10250/stats/summary/: dial tcp 10.199.183.218:10250: i/o timeout
I can't ping from the pod to the node where it is deployed.
I have added below config in metric server:
command:
- /metrics-server
- --kubelet-insecure-tls
- --kubelet-preferred-address-types=InternalIP
kubernetes heapster edited Nov 19 at 12:02
Emruz Hossain
84017
asked Nov 19 at 11:23
Hanna
11
New contributor
Hanna is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
I am trying to figure out why Metric server isn't collecting stats from the node where it is deployed (r2s13). There are 3 nodes in my cluster (1 master and 2 workers).
metric server version: 0.3.1
kubernetes version: 1.12 (installed with kubeadm)
CNI plugin: weave net
kubectl top node output:
NAME CPU(cores) CPU% MEMORY(bytes) MEMORY%
r2s12 344m 4% 3079Mi 12%
r2s14 67m 0% 1695Mi 21%
r2s13
In metric server log, I have the below line repeated (just for the node where the metric server is deployed r2s13):
E1023 15:28:14.643011 1 manager.go:102] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:r2s13: unable to fetch metrics from Kubelet r2s13 (10.199.183.218): Get https://10.199.183.218:10250/stats/summary/: dial tcp 10.199.183.218:10250: i/o timeout
I can't ping from the pod to the node where it is deployed.
I have added below config in metric server:
command:
- /metrics-server
- --kubelet-insecure-tls
- --kubelet-preferred-address-types=InternalIP
edited Nov 19 at 12:02
Emruz Hossain
84017
asked Nov 19 at 11:23
Hanna
11
New contributor
Hanna is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Have you tried to fix /etc/resolv.conf as @Rico suggested in stackoverflow.com/a/52230952/9929015 ?
– VKR
Nov 19 at 15:29
Yes the resolve.conf on each node contains all the nodes. and the ping between the nodes is OK; while I can't ping from inside the metric pod to the IP of its hosting node.
– Hanna
2 days ago
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am trying to figure out why Metric server isn't collecting stats from the node where it is deployed (r2s13). There are 3 nodes in my cluster (1 master and 2 workers).
metric server version: 0.3.1
kubernetes version: 1.12 (installed with kubeadm)
CNI plugin: weave net
kubectl top node output:
NAME CPU(cores) CPU% MEMORY(bytes) MEMORY%
r2s12 344m 4% 3079Mi 12%
r2s14 67m 0% 1695Mi 21%
r2s13
In metric server log, I have the below line repeated (just for the node where the metric server is deployed r2s13):
E1023 15:28:14.643011 1 manager.go:102] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:r2s13: unable to fetch metrics from Kubelet r2s13 (10.199.183.218): Get https://10.199.183.218:10250/stats/summary/: dial tcp 10.199.183.218:10250: i/o timeout
I can't ping from the pod to the node where it is deployed.
I have added below config in metric server:
command:
- /metrics-server
- --kubelet-insecure-tls
- --kubelet-preferred-address-types=InternalIP
edited Nov 19 at 12:02
Emruz Hossain
84017
asked Nov 19 at 11:23
Hanna
11
New contributor
Hanna is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I am trying to figure out why Metric server isn't collecting stats from the node where it is deployed (r2s13). There are 3 nodes in my cluster (1 master and 2 workers).
metric server version: 0.3.1
kubernetes version: 1.12 (installed with kubeadm)
CNI plugin: weave net
kubectl top node output:
NAME CPU(cores) CPU% MEMORY(bytes) MEMORY%
r2s12 344m 4% 3079Mi 12%
r2s14 67m 0% 1695Mi 21%
r2s13
In metric server log, I have the below line repeated (just for the node where the metric server is deployed r2s13):
E1023 15:28:14.643011 1 manager.go:102] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:r2s13: unable to fetch metrics from Kubelet r2s13 (10.199.183.218): Get https://10.199.183.218:10250/stats/summary/: dial tcp 10.199.183.218:10250: i/o timeout
I can't ping from the pod to the node where it is deployed.
I have added below config in metric server:
command:
- /metrics-server
- --kubelet-insecure-tls
- --kubelet-preferred-address-types=InternalIP
edited Nov 19 at 12:02
Emruz Hossain
84017
asked Nov 19 at 11:23
Hanna
11
New contributor
Hanna is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Nov 19 at 12:02
Emruz Hossain
84017
asked Nov 19 at 11:23
Hanna
11
New contributor
Hanna is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Nov 19 at 12:02
Emruz Hossain
84017
edited Nov 19 at 12:02
Emruz Hossain
84017
edited Nov 19 at 12:02
Emruz Hossain
84017
84017
asked Nov 19 at 11:23
Hanna
11
New contributor
Hanna is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 19 at 11:23
Hanna
11
asked Nov 19 at 11:23
Hanna
11
11
New contributor
Hanna is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Hanna is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Hanna is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Have you tried to fix /etc/resolv.conf as @Rico suggested in stackoverflow.com/a/52230952/9929015 ?
– VKR
Nov 19 at 15:29
Yes the resolve.conf on each node contains all the nodes. and the ping between the nodes is OK; while I can't ping from inside the metric pod to the IP of its hosting node.
– Hanna
2 days ago
add a comment |
Have you tried to fix /etc/resolv.conf as @Rico suggested in stackoverflow.com/a/52230952/9929015 ?
– VKR
Nov 19 at 15:29
Yes the resolve.conf on each node contains all the nodes. and the ping between the nodes is OK; while I can't ping from inside the metric pod to the IP of its hosting node.
– Hanna
2 days ago
Have you tried to fix /etc/resolv.conf as @Rico suggested in stackoverflow.com/a/52230952/9929015 ?
– VKR
Nov 19 at 15:29
Have you tried to fix /etc/resolv.conf as @Rico suggested in stackoverflow.com/a/52230952/9929015 ?
– VKR
Nov 19 at 15:29
Yes the resolve.conf on each node contains all the nodes. and the ping between the nodes is OK; while I can't ping from inside the metric pod to the IP of its hosting node.
– Hanna
2 days ago
Yes the resolve.conf on each node contains all the nodes. and the ping between the nodes is OK; while I can't ping from inside the metric pod to the IP of its hosting node.
– Hanna
2 days ago
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Hanna is a new contributor. Be nice, and check out our Code of Conduct.
Hanna is a new contributor. Be nice, and check out our Code of Conduct.
Hanna is a new contributor. Be nice, and check out our Code of Conduct.
Hanna is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53373584%2fmetric-server-unable-to-fetch-monitoring-data-from-the-node-where-his-pod-is-pla%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Have you tried to fix /etc/resolv.conf as @Rico suggested in stackoverflow.com/a/52230952/9929015 ?
– VKR
Nov 19 at 15:29
Yes the resolve.conf on each node contains all the nodes. and the ping between the nodes is OK; while I can't ping from inside the metric pod to the IP of its hosting node.
– Hanna
2 days ago