kubernetes autoscale having issues with heapster











up vote
0
down vote

favorite












I have heapster installed on kubernetes, i am trying to autoscale my pods.. but i keep seeing the following:



unable to get metrics for resource cpu: unable to fetch metrics from resource metrics API: the server could not find the requested resource (get pods.metrics.k8s.io)


The heapster service itself 



 I1009 14:22:21.014890       1 heapster.go:73] Heapster version v1.4.2

I1009 14:22:21.015226       1 configs.go:61] Using Kubernetes client with master "https://kubernetes.default" and version v1

I1009 14:22:21.015244       1 configs.go:62] Using kubelet port 10250

I1009 14:22:21.030070       1 heapster.go:196] Starting with Metric Sink

I1009 14:22:21.042806       1 heapster.go:106] Starting heapster on port 8082

E1009 14:30:05.000311       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready

E1009 14:30:05.000342       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready

E1009 14:30:05.000351       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready

E1009 14:30:05.000357       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready

E1009 14:30:05.000363       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready

E1009 14:30:05.000370       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready


I want to have autoscaling working with kubernetes, anyone have any ideas?



I know heapster is deprecated, but as of now i cannot chnage or upgrade to metrics server.. so could do with some help






kubernetes







share|improve this question




























    up vote
    0
    down vote

    favorite












    I have heapster installed on kubernetes, i am trying to autoscale my pods.. but i keep seeing the following:



    unable to get metrics for resource cpu: unable to fetch metrics from resource metrics API: the server could not find the requested resource (get pods.metrics.k8s.io)


    The heapster service itself 



     I1009 14:22:21.014890       1 heapster.go:73] Heapster version v1.4.2
    
I1009 14:22:21.015226       1 configs.go:61] Using Kubernetes client with master "https://kubernetes.default" and version v1
    
I1009 14:22:21.015244       1 configs.go:62] Using kubelet port 10250
    
I1009 14:22:21.030070       1 heapster.go:196] Starting with Metric Sink
    
I1009 14:22:21.042806       1 heapster.go:106] Starting heapster on port 8082
    
E1009 14:30:05.000311       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready
    
E1009 14:30:05.000342       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready
    
E1009 14:30:05.000351       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready
    
E1009 14:30:05.000357       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready
    
E1009 14:30:05.000363       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready
    
E1009 14:30:05.000370       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready


    I want to have autoscaling working with kubernetes, anyone have any ideas?



    I know heapster is deprecated, but as of now i cannot chnage or upgrade to metrics server.. so could do with some help






    kubernetes







    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I have heapster installed on kubernetes, i am trying to autoscale my pods.. but i keep seeing the following:



      unable to get metrics for resource cpu: unable to fetch metrics from resource metrics API: the server could not find the requested resource (get pods.metrics.k8s.io)


      The heapster service itself 



       I1009 14:22:21.014890       1 heapster.go:73] Heapster version v1.4.2
      
I1009 14:22:21.015226       1 configs.go:61] Using Kubernetes client with master "https://kubernetes.default" and version v1
      
I1009 14:22:21.015244       1 configs.go:62] Using kubelet port 10250
      
I1009 14:22:21.030070       1 heapster.go:196] Starting with Metric Sink
      
I1009 14:22:21.042806       1 heapster.go:106] Starting heapster on port 8082
      
E1009 14:30:05.000311       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready
      
E1009 14:30:05.000342       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready
      
E1009 14:30:05.000351       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready
      
E1009 14:30:05.000357       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready
      
E1009 14:30:05.000363       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready
      
E1009 14:30:05.000370       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready


      I want to have autoscaling working with kubernetes, anyone have any ideas?



      I know heapster is deprecated, but as of now i cannot chnage or upgrade to metrics server.. so could do with some help






      kubernetes







      share|improve this question















      I have heapster installed on kubernetes, i am trying to autoscale my pods.. but i keep seeing the following:



      unable to get metrics for resource cpu: unable to fetch metrics from resource metrics API: the server could not find the requested resource (get pods.metrics.k8s.io)


      The heapster service itself 



       I1009 14:22:21.014890       1 heapster.go:73] Heapster version v1.4.2
      
I1009 14:22:21.015226       1 configs.go:61] Using Kubernetes client with master "https://kubernetes.default" and version v1
      
I1009 14:22:21.015244       1 configs.go:62] Using kubelet port 10250
      
I1009 14:22:21.030070       1 heapster.go:196] Starting with Metric Sink
      
I1009 14:22:21.042806       1 heapster.go:106] Starting heapster on port 8082
      
E1009 14:30:05.000311       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready
      
E1009 14:30:05.000342       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready
      
E1009 14:30:05.000351       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready
      
E1009 14:30:05.000357       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready
      
E1009 14:30:05.000363       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready
      
E1009 14:30:05.000370       1 kubelet.go:280] Node ip-xxxxxx.eu-west-1.compute.internal is not ready


      I want to have autoscaling working with kubernetes, anyone have any ideas?



      I know heapster is deprecated, but as of now i cannot chnage or upgrade to metrics server.. so could do with some help






      kubernetes




      kubernetes






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 15 hours ago

























      asked 18 hours ago









      user1555190

      85342546




      85342546
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          I have once seen similar error. The problem was RBAC issue but the error log was misleading. Make sure you have provided get permission for pods.metrics.k8s.io resource.



          Check this similar question: Kubernetes Custom CRD: “Failed to list …: the server could not find the requested resource”




          Note: Fetching metrics from Heapster is deprecated as of Kubernetes 1.11. Ref: Horizontal Pod Autoscaler







          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














             

            draft saved


            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53371806%2fkubernetes-autoscale-having-issues-with-heapster%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            I have once seen similar error. The problem was RBAC issue but the error log was misleading. Make sure you have provided get permission for pods.metrics.k8s.io resource.



            Check this similar question: Kubernetes Custom CRD: “Failed to list …: the server could not find the requested resource”




            Note: Fetching metrics from Heapster is deprecated as of Kubernetes 1.11. Ref: Horizontal Pod Autoscaler







            share|improve this answer

























              up vote
              0
              down vote













              I have once seen similar error. The problem was RBAC issue but the error log was misleading. Make sure you have provided get permission for pods.metrics.k8s.io resource.



              Check this similar question: Kubernetes Custom CRD: “Failed to list …: the server could not find the requested resource”




              Note: Fetching metrics from Heapster is deprecated as of Kubernetes 1.11. Ref: Horizontal Pod Autoscaler







              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                I have once seen similar error. The problem was RBAC issue but the error log was misleading. Make sure you have provided get permission for pods.metrics.k8s.io resource.



                Check this similar question: Kubernetes Custom CRD: “Failed to list …: the server could not find the requested resource”




                Note: Fetching metrics from Heapster is deprecated as of Kubernetes 1.11. Ref: Horizontal Pod Autoscaler







                share|improve this answer












                I have once seen similar error. The problem was RBAC issue but the error log was misleading. Make sure you have provided get permission for pods.metrics.k8s.io resource.



                Check this similar question: Kubernetes Custom CRD: “Failed to list …: the server could not find the requested resource”




                Note: Fetching metrics from Heapster is deprecated as of Kubernetes 1.11. Ref: Horizontal Pod Autoscaler








                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered 15 hours ago









                Emruz Hossain

                82217




                82217






























                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53371806%2fkubernetes-autoscale-having-issues-with-heapster%23new-answer', 'question_page');
                    }
                    );

                    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







                    Popular posts from this blog

                    android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

                    Image
                    .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } 0 This is a simple project showing cubes on Unity, exported to android project and imported on Android studio. On maifest file it showed following warning: Expecting <uses-feature android:name="android.software.leanback" android:required="false" /> tag I have no information about it. And also on default emptyview android project does not use/mention this feature. I know it is required by TV's and such but why its not added by default? Why is this? And Should I concern about it? android unity3d
                    Read more

                    SQL update select statement

                    Image
                    0 I'm trying to update an entry in my database (postgresql). I'm having a problem with updating the query: INSERT INTO prices (price, product_id) SELECT product_price, commn_id FROM products_temp as prod WHERE NOT EXISTS (SELECT * FROM prices od WHERE prod.commn_id = od.product_id) OR prod.product_price != ( SELECT price FROM prices as p WHERE p.product_id = prod.commn_id order by p.end desc LIMIT 1 ) Query works fine when i delete: OR prod.product_price != ( SELECT price FROM prices as p WHERE p.product_id = prod.commn_id order by p.end desc LIMIT 1 ) So it seems to me that it's looping through this operation. My question is, how can I fix it? sql postgresql
                    Read more

                    'app-layout' is not a known element: how to share Component with different Modules

                    Image
                    0 My application was working fine until I decided to go with lazy loading: So, my shared component looks like this: import { Component, Renderer2 } from '@angular/core'; export interface FormModel { captcha?: string; } @Component({ selector: 'app-layout', templateUrl: './app-layout.component.html', styleUrls: ['./app-layout.css'] }) export class FullLayoutComponent { } app-layout.component.ts I am using this component in my Another component say school-home.component.html like this: <app-layout> </app-layout> and it was working fine until I created a Module school-home.module.ts like this: import { NgModule } from '@angular/core'; import { CommonModule } from '@angular/common'; import { SchoolhomeRoutingModule
                    Read more