Como entender e combinar estratégias de escalonamento automático do GKE avaliações

HARI MEGHANA K. · Revisado há over 1 year

clear as sky

Michael Pintanta Dwides P. · Revisado há over 1 year

Sree Ramachandra G. · Revisado há over 1 year

Ashwinder S. · Revisado há over 1 year

Aleix H. · Revisado há over 1 year

Yashpalsinh J. · Revisado há over 1 year

Michał B. · Revisado há over 1 year

Aniket K. · Revisado há over 1 year

Manuel Eiras C. · Revisado há over 1 year

Internet and resource issues.

Dave H. · Revisado há over 1 year

Justin K. · Revisado há over 1 year

Eduardo A. · Revisado há over 1 year

A lot of these commands take much longer to finish than the lab recommends. For example, it's taking 5-8 full minutes for things that this lab says should take "a minute or two". It makes the lab feel very choppy.

Michelle C. · Revisado há over 1 year

EL MEHDI A. · Revisado há over 1 year

Maciej C. · Revisado há over 1 year

mreza f. · Revisado há over 1 year

Fatokunbo S. · Revisado há over 1 year

Alexander L. · Revisado há over 1 year

Muhammad Umer R. · Revisado há over 1 year

Dinesh J. · Revisado há over 1 year

Ravi S. · Revisado há over 1 year

Andrew Borg Ning C. · Revisado há over 1 year

Pod is blocking scale down because it doesn’t have enough Pod Disruption Budget (PDB) Details Scale down of underutilized node is blocked because it has a Pod running on it which doesn’t have enough PDB to allow eviction of the pod. Refer to logs for more details. Recommended actions Review PDB rules of Pod in the log event and update the rules if necessary. { "insertId": "c92d7e13-7e0d-4cad-841d-acc2a404551d@a1", "jsonPayload": { "noDecisionStatus": { "noScaleDown": { "nodes": [ { "reason": { "parameters": [ "event-exporter-gke-7d996c57bf-vs6fl" ], "messageId": "no.scale.down.node.pod.not.enough.pdb" }, "node": { "name": "gke-scaling-demo-default-pool-32fbf8c9-vkks", "cpuRatio": 40, "memRatio": 7, "mig": { "name": "gke-scaling-demo-default-pool-32fbf8c9-grp", "nodepool": "default-pool", "zone": "us-east1-d" } } } ], "nodesTotalCount": 1 }, "measureTime": "1715246108" } }, "resource": { "type": "k8s_cluster", "labels": { "cluster_name": "scaling-demo", "location": "us-east1-d", "project_id": "qwiklabs-gcp-01-fb3dcc713c69" } }, "timestamp": "2024-05-09T09:15:08.242073284Z", "logName": "projects/qwiklabs-gcp-01-fb3dcc713c69/logs/container.googleapis.com%2Fcluster-autoscaler-visibility", "receiveTimestamp": "2024-05-09T09:15:09.270697750Z" } i needed to change maxUnavailable: to 3 and then node went down by 1 number

Naveen V. · Revisado há over 1 year

Arvind Kumar M. · Revisado há over 1 year

Guda M. · Revisado há over 1 year