Noelantogerorge opened a new issue, #7493:
URL: https://github.com/apache/cloudstack/issues/7493

   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and main branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete 
the comments.
   -->
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Improvement Request
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   Kubernetes
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on main 
branch.
   -->
   
   4.18
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, 
advanced networking, etc.  N/A otherwise
   -->
   
   advanced networking used
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   All servers on ubuntu 22.04
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   
   When a kubernetes cluster is spinned up metric API is not available. We will 
have to configure metric API manually. Without metric API horizontal pod auto 
scale will not work and also kubernetes admin won't able to know the 
utilisation each pod and node is accuring.
   
   There are different way to enable metric API but I feel more easy on below 
steps.
   
   Step 1 : Check metric API
                 kubectl top nodes
                 (it will show metric API not available error)
   
   Step2: Install metric API from kubernetes git
                kubectl apply -f 
https://github.com/kubernetes-sigs/metrics-server/releases/latest/download/components.yaml
   
   Step 3: Check metric pod is running
               Kubectl -n kube-system get pods
   
   Step 4: Edit metric server deployement and below line
                kubectl -n kube-system edit deploy metrics-server 
                <Add below lines after metric-resolution=15s in containers tag>
                command:
           - /metrics-server
           - --kubelet-insecure-tls
           - --kubelet-preferred-address-types=InternalIP
           
   Step 5: Check metric API
               kubectl top nodes
   
   ##### STEPS TO REPRODUCE
   <!--
   For bugs, show exactly how to reproduce the problem, using a minimal 
test-case. Use Screenshots if accurate.
   
   For new features, show how the feature would be used.
   -->
   
   Just bring up a cluster and type kubectl top nodes command will get metric 
API unavailable message
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   If a user bring up a kubernetes cluster they should get maximum componenets 
on cluster so that they don't want to go around for each. If any changes on 
this can be done please do the needful so it can help users using kubernetes on 
cloudstack


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to