Como configurar um armazenamento permanente para o Google Kubernetes Engine avaliações

Saravanakumar N. · Revisado há over 1 year

Nicola F. · Revisado há over 1 year

Lorenzo B. · Revisado há over 1 year

Luigi G. · Revisado há over 1 year

Paolo L. · Revisado há over 1 year

Luca M. · Revisado há over 1 year

Nazar H. · Revisado há over 1 year

Michele D. · Revisado há over 1 year

Gaetano Alberto P. · Revisado há over 1 year

Vojtech K. · Revisado há over 1 year

Ricardo F. · Revisado há over 1 year

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. · Revisado há over 1 year

Michael N. · Revisado há over 1 year

ALLEN R. · Revisado há over 1 year

Mason B. · Revisado há over 1 year

apex c. · Revisado há over 1 year

Kevin H. · Revisado há over 1 year

Dominik Ż. · Revisado há over 1 year

Jordan W. · Revisado há over 1 year

Hubert K. · Revisado há over 1 year

Offei L. · Revisado há over 1 year

Dawid W. · Revisado há over 1 year

Dawid S. · Revisado há over 1 year

MIchal L. · Revisado há over 1 year

Nirmala N. · Revisado há over 1 year