Running kubectl command should not throw error message "couldn't get resource list for external.metrics.k8s.io/v1beta1: the server is currently unable to handle the request" This was an issue while running 2.9.3 but after deploying the dummy-metric the error got stopped, but after the upgr...
1 manager.go:111] unable to fully collect metrics: unable to fully scrape metrics from source kubelet_summary:172.20.0.217: unable to get CPU for container "java-springboot-web" in pod java-springboot-web-b8cff79f5-w9bqq on node "172.20.0.217", discarding data: missing cpu usage metric...
没有配置 --kubelet-preferred-address-types=InternalIP,Hostname,InternalDNS,ExternalDNS,ExternalIP metrics-server 会有类似如下的报错 E0907 14:29:51.774592 1 manager.go:102] unable to fully collect metrics: [unable to fully scrape metrics from source kubelet_summary:<node_name>: unable to fetch ...
first error is: failed to get pods metric value: unable to get metric istio_requests_per_second: unable to fetch metrics from custom metrics API: the server could not find the metric istio_requests_per_second for pods
metric-resolution:从 kubelet 采集数据的周期,默认为 60s kubelet-preferred-address-types:优先使用 InternalIP 来访问 kubelet,这样可以避免节点名称没有 DNS 解析记录时,通过节点名称调用节点 kubelet API 失败的情况 默认为 Hostname,InternalDNS,InternalIP,ExternalDNS,ExternalIP ...
192.168.150.0/24 connection to an external network. We have the following routing table: Console Copy === Interface List 13...c4 34 6b 60 42 9a ...Intel(R) Ethernet Connection I217-LM 11...68 05 ca 20 ac b4 ...Intel(R) Gigabit CT2 Desktop Adapter 1...Software Loopbac...
metadata: labels: k8s-app: metrics-server spec: containers: - args: - --cert-dir=/tmp - --secure-port=4443 - --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname - --kubelet-use-node-status-port - --kubelet-insecure-tls #添加 - --metric-resolution=30s #添加 image: k8s....
Metric Name: OI|connector|NetOps OI Connector|NETOPS_001|NetOps Performance Management|NETOPS_001_PM_001|Entity:IntervalSinceLastSuccessfulPush Metric Value: 165.0 When attempting to restart the OI connector in PM, I get the following on the OI connector log ...
web: image: 'gitlab/gitlab-ce:latest' restart: always hostname: 'mygitlabserver' environment: GITLAB_OMNIBUS_CONFIG: | external_url 'https://mygitlabserver' #nginx['redirect_http_to_https'] = true gitlab_rails['env'] = { 'prometheus_multiproc_dir' => '/dev/shm' } prometheus['...
Do you get to the credential prompt, do you see an endless "connecting" window, does the connect button do anything? What OS are we talking about (Linux, macOS, Windows)? The logs will almost always tell you exactly what the issue is if you look at them on the endpoint in ...