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

This is a known issue that has always existed. Please subscribe these issues if you want to be notified about the progress/resolution: https://github.com/kubernetes/ingress-gce/issues/136 https://github.com/kubernetes/kubernetes/issues/4630 If you're using Service.type=LoadBalancer, you can use

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

I have posted solutions and references on the below link. Kindly check https://waterplacid.com/k8-docker/ On Friday, April 13, 2018 at 5:48:03 AM UTC+5:30, Blake Acheson wrote: > Yes...this is occurring after deleting deployments and services. > > On Thu, Apr 12, 2018, 7:15 PM Rodrigo Campos,

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

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

FYI, there is on going effort to close the leak. On Thursday, April 12, 2018 at 4:15:45 PM UTC-7, Rodrigo Campos wrote: > Have you tried deleting the services before and that stuff? > > On Thursday, April 12, 2018, wrote: > When deleting deployments and clusters

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

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

[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