[kubernetes-users] Kubernetes Engine ImagePullBackOff for all images across all clusters

Kubernetes engine cannot pull any images from the container registry. Receiving the error "unknown blob". This is happening on services that haven't been changes in months. Started at 9pm ET. -- You received this message because you are subscribed to the Google Groups "Kubernetes user

[kubernetes-users] Kubernetes Engine all pull image commands failing: unknown blob

docker pull us.gcr.io/xxx/worker:production-v2production-v2: Pulling from xxx/worker297061f60c36: Pulling fs layere9ccef17b516: Pulling fs layerdbc33716854d: Pulling fs layer8fe36b178d25: Pulling fs layer686596545a94: Pulling fs layer5cc528115552: Pulling fs layerd56c0a66c903: Pulling fs

[kubernetes-users] GKE Failed automated upgrade

My cluster upgraded on the weekend to 1.8.8-gke.0. Now the following error is reporting twice (it's a regional cluster): All cluster resources were brought up, but the cluster API is reporting that component "kube-apiserver" from endpoint "gke-xxx" is unhealthy -- You received this message

Re: [kubernetes-users] Kubernetes engine not cleaning up after itself (firewall rules + load balancers)

Yes...this is occurring after deleting deployments and services. On Thu, Apr 12, 2018, 7:15 PM Rodrigo Campos, wrote: > Have you tried deleting the services before and that stuff? > > On Thursday, April 12, 2018, wrote: > >> When deleting

[kubernetes-users] Kubernetes engine not cleaning up after itself (firewall rules + load balancers)

When deleting deployments and clusters kubernetes engine is leaving behind a mess of orphaned load balancers and firewall rules. -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q" group. To unsubscribe from this group and stop