Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Metrics server unable to fetch the target metrics after downloading components.yaml file from the metrics server installation URL . #1454

Open
PranitRout07 opened this issue Mar 26, 2024 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@PranitRout07
Copy link

ISSUE : Metrics server unable to fetch the target metrics after downloading components.yaml file from the metrics server installation URL .

Metrics Server Installation URL : https://github.com/kubernetes-sigs/metrics-server/releases/latest/download/components.yaml

ISSUE DESCRIPTION :

Here i have first downloaded the components.yaml using the above URL . Then applied the components.yaml , but it is unable to detect the target metrics . Here in the below screenshot you can see the hpa resource is unable fetch the target metrics .

if not used

Then added the following lines at line number 140 .

        command:
        - /metrics-server
        - --kubelet-insecure-tls
        - --kubelet-preferred-address-types=InternalIP
why this

After adding the lines , then again i have applied the components.yaml file using kubectl . Now hpa can detect the target metrics .

after adding

Question

Why the lines are not directly included at line number 140 in the components.yaml , so that it can work directly after downloaded from the URL ?

/kind bug

@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Mar 26, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If metrics-server contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Mar 26, 2024
@Chander84
Copy link

I have a different experience, If I download the components.yaml file using the https://github.com/kubernetes-sigs/metrics-server/releases/latest/download/components.yaml I am getting empty components.yaml. I am using EKS 1.26 version with fargate nodes. Please suggest me for the fix.

sh "curl -o components.yaml https://github.com/kubernetes-sigs/metrics-server/releases/latest/download/components.yaml"
sh "ls -ltr"

output:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

3 participants