{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes-incubator/metrics-server/issues/133","repository_url":"https://api.github.com/repos/kubernetes-incubator/metrics-server","labels_url":"https://api.github.com/repos/kubernetes-incubator/metrics-server/issues/133/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes-incubator/metrics-server/issues/133/comments","events_url":"https://api.github.com/repos/kubernetes-incubator/metrics-server/issues/133/events","html_url":"https://github.com/kubernetes-incubator/metrics-server/issues/133","id":356560252,"node_id":"MDU6SXNzdWUzNTY1NjAyNTI=","number":133,"title":"unable to fetch pod metrics for pod - running metric-server on Kubernetes 1.9","user":{"login":"antoniogomezalvarado","id":32959190,"node_id":"MDQ6VXNlcjMyOTU5MTkw","avatar_url":"https://avatars3.githubusercontent.com/u/32959190?v=4","gravatar_id":"","url":"https://api.github.com/users/antoniogomezalvarado","html_url":"https://github.com/antoniogomezalvarado","followers_url":"https://api.github.com/users/antoniogomezalvarado/followers","following_url":"https://api.github.com/users/antoniogomezalvarado/following{/other_user}","gists_url":"https://api.github.com/users/antoniogomezalvarado/gists{/gist_id}","starred_url":"https://api.github.com/users/antoniogomezalvarado/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/antoniogomezalvarado/subscriptions","organizations_url":"https://api.github.com/users/antoniogomezalvarado/orgs","repos_url":"https://api.github.com/users/antoniogomezalvarado/repos","events_url":"https://api.github.com/users/antoniogomezalvarado/events{/privacy}","received_events_url":"https://api.github.com/users/antoniogomezalvarado/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":8,"created_at":"2018-09-03T16:29:50Z","updated_at":"2018-09-12T14:41:32Z","closed_at":null,"author_association":"NONE","body":"**Current setup**\r\nI'm running Kubernetes 1.9 which has been setup with Kops 1.9, currently running heapster and I which to migrate to the new metrics-server in order to expose CPU/Memory/Storage metrics to be used by HPA.\r\n\r\n**What version am I running?**\r\n` kubectl version`\r\n\r\n`Client Version: version.Info{Major:\"1\", Minor:\"10\", GitVersion:\"v1.10.1\", GitCommit:\"d4ab47518836c750f9949b9e0d387f20fb92260b\", GitTreeState:\"clean\", BuildDate:\"2018-04-13T22:29:03Z\", GoVersion:\"go1.9.5\", Compiler:\"gc\", Platform:\"darwin/amd64\"}\r\nServer Version: version.Info{Major:\"1\", Minor:\"9\", GitVersion:\"v1.9.0\", GitCommit:\"925c127ec6b946659ad0fd596fa959be43f0cc05\", GitTreeState:\"clean\", BuildDate:\"2017-12-15T20:55:30Z\", GoVersion:\"go1.9.2\", Compiler:\"gc\", Platform:\"linux/amd64\"}`\r\n\r\n**Whats the issue?**\r\nAfter installing metrics-server using the following instructions here: https://github.com/kubernetes-incubator/metrics-server (`kubectl create -f deploy/1.8+/`)\r\nI'm seeing the following errors in the metrics-server pod logs:\r\n\r\n`E0903 15:56:05.116049       1 reststorage.go:98] unable to fetch pod metrics for pod x/geodrive-server-1562483932-xb2kq: no metrics known for pod \"x/geodrive-server-1562483932-xb2kq\"\r\nE0903 15:56:05.116075       1 reststorage.go:98] unable to fetch pod metrics for pod x/geodrive-server-1562483932-ljxn2: no metrics known for pod \"x/geodrive-server-1562483932-ljxn2\"\r\nE0903 15:56:07.506634       1 manager.go:102] unable to fully collect metrics: [unable to fully scrape metrics from source kubelet_summary:ip-172-31-104-76.us-west-2.compute.internal: unable to fetch metrics from Kubelet ip-172-31-104-76.us-west-2.compute.internal (ip-172-31-104-76.us-west-2.compute.internal): Get https://ip-172-31-104-76.us-west-2.compute.internal:10250/stats/summary/: x509: certificate signed by unknown authority, unable to fully scrape metrics from source kubelet_summary:ip-172-31-109-239.us-west-2.compute.internal: unable to fetch metrics from Kubelet ip-172-31-109-239.us-west-2.compute.internal (ip-172-31-109-239.us-west-2.compute.internal): Get https://ip-172-31-109-239.us-west-2.compute.internal:10250/stats/summary/: x509: certificate signed by unknown `\r\n\r\n`kubectl describe hpa`\r\n\r\n`Name:                                                  x-nexpresso\r\nNamespace:                                             x\r\nLabels:                                                <none>\r\nAnnotations:                                           <none>\r\nCreationTimestamp:                                     Mon, 03 Sep 2018 17:17:51 +0300\r\nReference:                                             Deployment/x-nexpresso\r\nMetrics:                                               ( current / target )\r\n  resource cpu on pods  (as a percentage of request):  <unknown> / 80%\r\nMin replicas:                                          1\r\nMax replicas:                                          64\r\nConditions:\r\n  Type           Status  Reason                   Message\r\n  AbleToScale    True    SucceededGetScale        the HPA controller was able to get the target's current scale\r\n  ScalingActive  False   FailedGetResourceMetric  the HPA was unable to compute the replica count: unable to get metrics for resource cpu: no metrics returned from heapster\r\nEvents:\r\n  Type     Reason                        Age                From                       Message\r\n  Warning  FailedGetResourceMetric       7m (x215 over 2h)  horizontal-pod-autoscaler  unable to get metrics for resource cpu: no metrics returned from heapster\r\n  Warning  FailedComputeMetricsReplicas  2m (x225 over 2h)  horizontal-pod-autoscaler  failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from heapster`\r\n\r\n**What do I expect?**\r\nI was under the impression that since 1.9 ```--horizontal-pod-autoscaler-use-rest-clients=true``` is default and once installing metrics-server it should take place and heapster won't work anymore, but now none of them is working. What am I missing?"},"comment":{"url":"https://api.github.com/repos/kubernetes-incubator/metrics-server/issues/comments/420673961","html_url":"https://github.com/kubernetes-incubator/metrics-server/issues/133#issuecomment-420673961","issue_url":"https://api.github.com/repos/kubernetes-incubator/metrics-server/issues/133","id":420673961,"node_id":"MDEyOklzc3VlQ29tbWVudDQyMDY3Mzk2MQ==","user":{"login":"DirectXMan12","id":119737,"node_id":"MDQ6VXNlcjExOTczNw==","avatar_url":"https://avatars1.githubusercontent.com/u/119737?v=4","gravatar_id":"","url":"https://api.github.com/users/DirectXMan12","html_url":"https://github.com/DirectXMan12","followers_url":"https://api.github.com/users/DirectXMan12/followers","following_url":"https://api.github.com/users/DirectXMan12/following{/other_user}","gists_url":"https://api.github.com/users/DirectXMan12/gists{/gist_id}","starred_url":"https://api.github.com/users/DirectXMan12/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/DirectXMan12/subscriptions","organizations_url":"https://api.github.com/users/DirectXMan12/orgs","repos_url":"https://api.github.com/users/DirectXMan12/repos","events_url":"https://api.github.com/users/DirectXMan12/events{/privacy}","received_events_url":"https://api.github.com/users/DirectXMan12/received_events","type":"User","site_admin":false},"created_at":"2018-09-12T14:41:32Z","updated_at":"2018-09-12T14:41:32Z","author_association":"CONTRIBUTOR","body":"@embik if you can figure out which CA the kubelet certs are signed with, that would be useful to know.  It's probably going to boil down to us needing to support a different CA for connecting to Kubelet, but I'd like to make sure that's the issue first."}}
{"actor":{"display_login":"DirectXMan12"}}