Delete Deployment / ReplicaSet not working

[stevesloka]

I'm developing a client which is consuming the k8s using the client-go. I'm creating Deployments with the client and they work great, but when I try and delete, the deployments delete but the pods stay running.

I've also added logic to delete the ReplicaSets and they delete, but the pods still stay running.

I'm currently using tag v2.0.0-alpha.1

[lavalamp]

What version of Kubernetes is the cluster are you running against? Until the deployment controller begins using the GC, you'll need to scale the deployment to zero before deleting it. That change should be in 1.6 if it didn't make 1.5.

…

On Fri, Feb 3, 2017 at 12:20 PM, Steve Sloka ***@***.***> wrote: I'm developing a client which is consuming the k8s using the client-go. I'm creating Deployments with the client and they work great, but when I try and delete, the deployments delete but the pods stay running. I've also added logic to delete the ReplicaSets and they delete, but the pods still stay running. I'm currently using tag v2.0.0-alpha.1 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#91>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAngluFwUfuG1aB1Ayfq_2F0s2asNvF4ks5rY4v5gaJpZM4L2w9A> .

[stevesloka]

Right now I'm on v1.5.1. I can try scaling to zero first.

[lavalamp]

Yeah, I think it may have just missed the 1.5 cut.

…

On Fri, Feb 3, 2017 at 12:51 PM, Steve Sloka ***@***.***> wrote: Right now I'm on v1.5.1. I can try scaling to zero first. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#91 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAngltUPy7IuOXZLdDtN33_H_G8g9wJkks5rY5NAgaJpZM4L2w9A> .

[stevesloka]

Thanks for the help @lavalamp that worked by scaling it down first. I had to do the same for my StatefulSet as well.

[lavalamp]

Great! Just to repeat myself, this is an API thing, not a client thing. The API ought to do what people expect after using kubectl, but it doesn't (because kubectl manually does two things). This should be significantly ameliorated once all the controller types use the GC. Currently I think only RS/RC do so.

…

On Fri, Feb 3, 2017 at 7:33 PM, Steve Sloka ***@***.***> wrote: Closed #91 <#91>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#91 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAngluGtfvewjncR8J69NuHByx2b53KSks5rY_FwgaJpZM4L2w9A> .