[kubernetes-users] [SURVEY] enable ETCDCTL_API=3 by default (for etcdctl)

Hi, Now that etcd v3 has been out almost for 2 years https://github.com/coreos/etcd/releases/tag/v3.0.0 etcd team wants to enable ETCDCTL_API=3 by default for upcoming v3.4 release (planned for this summer). All v2 APIs and store will be still preserved until v4. We just want to promote etcd v3

[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

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

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