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

AKS 1.24 - * spec.template.spec.containers[0].resources.requests: Invalid value: "100m": must be less than or equal to cpu limit * spec.template.spec.containers[0].resources.requests: Invalid value: "200Mi": must be less than or equal to memory limit #1205

Open
regaltopax opened this issue Mar 8, 2023 · 5 comments
Assignees
Labels
kind/support Categorizes issue or PR as a support question. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@regaltopax
Copy link

Hi,

I am running into this issue when running an AKS cluster with 1.24 and 1.25 versions.

Command used
kubectl apply -f https://github.com/kubernetes-sigs/metrics-server/releases/download/metrics-server-helm-chart-3.8.3/components.yaml

This error is consistent no matter the version of metrics server used on the cluster.
AKS 1.23 cluster doesnt have the issue. I also do not see this issue on EKS 1.24 either

Error
The Deployment "metrics-server" is invalid:

  • spec.template.spec.containers[0].resources.requests: Invalid value: "100m": must be less than or equal to cpu limit
  • spec.template.spec.containers[0].resources.requests: Invalid value: "200Mi": must be less than or equal to memory limit

I have 2 nodepools with the same vm size Standard_D8_v3, which has 8vcpu's and 32GiB Memory

kubectl get nodes output
NAME CPU(cores) CPU% MEMORY(bytes) MEMORY%
aks-pool1-xxx-vmss000000 110m 1% 4032Mi 14%
aks-default-xxx-vmss000000 175m 2% 3599Mi 12%

AKS 1.24

My current workaround was to download the chart, remove the resource section, and run which works, but its not ideal since it does not have the necessary resource requirement

Happy to provide further information
/kind support

@k8s-ci-robot k8s-ci-robot added kind/support Categorizes issue or PR as a support question. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 8, 2023
@dgrisonnet
Copy link
Member

/triage accepted
/assign @yangjunmyfm192085

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Mar 9, 2023
@yangjunmyfm192085
Copy link
Contributor

Hi, @regaltopax, Please check whether the kubernetes cluster is configured with LimitRange?

@regaltopax
Copy link
Author

Hi @yangjunmyfm192085 .
I checked limits on the cluster, there is no limitrange applied on it

kubectl get limits -A
No resources found

@dankiki
Copy link

dankiki commented Jul 11, 2023

explicitly specifying resource limits along with the resource requests does make it work on AKS 1.25

@anachronic
Copy link

Same thing happened to me in AKS. Turns out metrics server was already installed and I think the new deployment was somehow clashing with the existent one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

6 participants