![]() ![]() In my deployment i just specified resources and that helped me to get HPA running apiVersion: apps/v1Īfter applying resource limit to my deployment HPA started working for me. NAME REFERENCE TARGETS MINPODS MAXPODS REPLICAS AGEīackend-iam-deployment Deployment/backend-iam-deployment 36278272/100Mi, /50% 1 10 1 10m I have deployed over EKS and i was facing the same issue. So we can now download this file, curl -L -output components.yamlĪdd -kubelet-insecure-tls under args (L88) to the metrics-server deployment and run kubectl apply -f components.yaml The repo now recommends installing it like this: apply -f Most of the above steps hold true except the metrics-server has changed and that file does not exist anymore. Using the OpenShift Container Platform CLI, you can create a horizontal pod autoscaler (HPA) to automatically scale an existing Deployment, DeploymentConfig. It should now show the current cpu usage. Remove and add the autoscaler to your deployment again. yaml, write this instead: kubectl apply -f deploy/1.8+) Image: /metrics-server-amd64:v0.3.1Īdd metrics-server to your Kubernetes instance with kubectl create -f deploy/1.8+ (if errors with the. Do this only for Docker, and not for production deployments of metrics-server: containers: The new section will instruct metrics-server to allow for an insecure communications session (don't verify the certs involved). Here are the full steps I took to get things working:ĭelete any previous instance of metrics-server from your Kubernetes instance with kubectl delete -n kube-system deployments.apps metrics-serverĮdit the file deploy/1.8+/metrics-server-deployment.yaml to override the default command by adding a command section that didn't exist before. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |