Configurer un stockage persistant pour Google Kubernetes Engine avis

Shantiranjan G. · Examiné il y a presque 2 ans

Bhaggya G. · Examiné il y a presque 2 ans

Sudeep N. · Examiné il y a presque 2 ans

Saravanakumar N. · Examiné il y a presque 2 ans

Nicola F. · Examiné il y a presque 2 ans

Lorenzo B. · Examiné il y a presque 2 ans

Luigi G. · Examiné il y a presque 2 ans

Paolo L. · Examiné il y a presque 2 ans

Luca M. · Examiné il y a presque 2 ans

Nazar H. · Examiné il y a presque 2 ans

Michele D. · Examiné il y a presque 2 ans

Gaetano Alberto P. · Examiné il y a presque 2 ans

Vojtech K. · Examiné il y a presque 2 ans

Ricardo F. · Examiné il y a presque 2 ans

One of my pods would never come up. This is the error Warning FailedScheduling 4m36s gke.io/optimize-utilization-scheduler 0/2 nodes are available: 1 Insufficient cpu, 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/2 nodes are available: 1 No preemption victims found for incoming pod, 1 Preemption is not helpful for scheduling.. Normal TriggeredScaleUp 4m20s cluster-autoscaler pod triggered scale-up: [{https://www.googleapis.com/compute/v1/projects/qwiklabs-gcp-02-12bbb1ac4514/zones/europe-west4-a/instanceGroups/gk3-autopilot-cluster-1-pool-2-c4aeaa01-grp 1->2 (max: 1000)}] Warning FailedScaleUp 3m23s cluster-autoscaler Node scale up in zones europe-west4-a associated with this pod failed: GCE quota exceeded. Pod is at risk of not being scheduled. Warning FailedScheduling 90s (x5 over 3m56s) gke.io/optimize-utilization-scheduler 0/2 nodes are available: 1 Insufficient cpu, 1 node(s) had volume node affinity conflict. preemption: 0/2 nodes are available: 1 No preemption victims found for incoming pod, 1 Preemption is not helpful for scheduling.. Normal NotTriggerScaleUp 90s cluster-autoscaler pod didn't trigger scale-up (it wouldn't fit if a new node is added): 14 node(s) had volume node affinity conflict, 1 node(s) had untolerated taint {cloud.google.com/gke-quick-remove: true}, 3 Insufficient cpu, 3 Insufficient memory, 7 in backoff after failed scale-up

Keith P. · Examiné il y a presque 2 ans

Michael N. · Examiné il y a presque 2 ans

ALLEN R. · Examiné il y a presque 2 ans

Mason B. · Examiné il y a presque 2 ans

apex c. · Examiné il y a presque 2 ans

Kevin H. · Examiné il y a presque 2 ans

Dominik Ż. · Examiné il y a presque 2 ans

Jordan W. · Examiné il y a presque 2 ans

Hubert K. · Examiné il y a presque 2 ans

Offei L. · Examiné il y a presque 2 ans

Dawid W. · Examiné il y a presque 2 ans