Well, it's not hanging forever, but takes abnormal long time to return.

@yifan-gu, we don't check if the replication controllers have the same selector, but we should (#2210). It should not allow you to create the second replication controller.

@yujuhong I was expecting this because it is confusing what if the two rc have different numbers...

What if you do --cascade=false for the delete command? I hope that actually completes.

Sent from my iPhone

On May 20, 2015, at 8:03 PM, Yifan Gu notifications@github.com wrote:

$ cat t1.yaml
apiVersion: v1beta3
kind: ReplicationController
metadata:
name: kube-nginx1
namespace: default
spec:
replicas: 1
selector:
k8s-app: kube-nginx1
template:
metadata:
labels:
k8s-app: kube-nginx1
spec:
containers:
- name: nginx
image: nginx

$ cat t2.yaml
apiVersion: v1beta3
kind: ReplicationController
metadata:
name: kube-nginx2
namespace: default
spec:
replicas: 1
selector:
k8s-app: kube-nginx1
template:
metadata:
labels:
k8s-app: kube-nginx1
spec:
containers:
- name: nginx
image: nginx

$ kubectl create -f t1.yaml
replicationcontrollers/kube-nginx1
$ kubectl create -f t2.yaml
replicationcontrollers/kube-nginx2
$ kubectl delete -f t2.yaml (hangs forever, never returns)

$ kubectl get rc
kube-nginx1 nginx nginx k8s-app=kube-nginx1 1
kube-nginx2 nginx nginx k8s-app=kube-nginx1 0
—
Reply to this email directly or view it on GitHub.

@derekwaynecarr --cascade=false works, seems should be covered by #2210. Thanks!

@derekwaynecarr --cascade=false indeed worked for me as well. However, without cleaning out the resources in a cascade fashion, would it eventually clog up k8s server? Who's going to do the garbage collection?

server side garbage collection is alpha and on by default in 1.4.

On Tuesday, September 20, 2016, Ye Wang notifications@github.com wrote:

@derekwaynecarr https://github.com/derekwaynecarr --cascade=false
indeed worked for me as well. However, without cleaning out the resources
in a cascade fashion, would it eventually clog up k8s server? Who's going
to do the garbage collection?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#8598 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF8dbGKQqQTdY8h7HJBn-H14C8PnI81lks5qsDsugaJpZM4EinI7
.