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

[Blake Acheson]

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 discussion and Q" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

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

[Blake Acheson]

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 layer31abb7079d25: Pulling fs 
layera252d058b80f: Pulling fs layerea3b0a25c7e8: Pulling fs 
layer1c6e3098a743: Pulling fs layercda934bf9e69: Pulling fs 
layerfbd9152eea97: Pulling fs layer5d095acb48c7: Pulling fs 
layerd96347de35f4: Pulling fs layer57a23b569ef6: Pulling fs 
layerd472c202ceb1: Pulling fs layer9c819306ec67: Pulling fs 
layer34a81fd6fea7: Pulling fs layer832b725afa78: Pulling fs 
layerb012b9ac685c: Pulling fs layere032ac141289: Pulling fs 
layera34780738ff0: Pulling fs layercda934bf9e69: Download 
complete2f249ebe6af2: Download complete7ef5f73d8bd2: Download 
complete148e4544855c: Download complete4beb693390d9: Download 
completed560635f8213: Download complete4694cd6c162c: Download 
completef74f5b348a6d: Download completef9c61494ba3d: Download 
completeba566e938ad2: Download complete0658a2879b3f: Download 
completeff53dec2a776: Download complete4f94eb00ab4b: Download 
complete1527b9c14c24: Download completeunknown blob

-- 
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 receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

[kubernetes-users] GKE Failed automated upgrade

[blake . acheson]

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 because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

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

[Blake Acheson]

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 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 receiving emails from it, send an
>> email to kubernetes-users+unsubscr...@googlegroups.com.
>> To post to this group, send email to kubernetes-users@googlegroups.com.
>> Visit this group at https://groups.google.com/group/kubernetes-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Kubernetes user discussion and Q" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/kubernetes-users/CGKXyusrekg/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> kubernetes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to kubernetes-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/kubernetes-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

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

[blake . acheson]

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 receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.