crinit init should not fail if the resources already exist about cluster-registry HOT 7 CLOSED

Also see kubernetes/kubernetes#47159

from cluster-registry.

I'm running into this. there are quite a few resources that I have to clean up manually when re-running crinit.
Here's the list of commands I needed to run in order to get my cluster cleaned up and ready to launch crinit again:

kc delete svc/first-cluster-reg -n clusterregistry ns/clusterregistry clusterroles/clusterregistry.k8s.io:apiserver clusterrolebindings/clusterregistry.k8s.io:apiserver clusterrolebindings/clusterregistry.k8s.io:apiserver-auth-delegator clusterrolebindings/clusterregistry.k8s.io:extension-apiserver-authentication-reader apiservices/v1alpha1.clusterregistry.k8s.io; kc delete rolebindings/clusterregistry.k8s.io:extension-apiserver-authentication-reader -n kube-system

from cluster-registry.

Thanks @G-Harmon! Yep, we need to look at introducing a delete subcommand or eventually use helm, to make this simpler. I use the following:

kubectl delete ns/clusterregistry clusterrole/clusterregistry.k8s.io:apiserver clusterrolebinding/clusterregistry.k8s.io:apiserver clusterrolebinding/clusterregistry.k8s.io:apiserver-auth-delegator; kubectl -n kube-system delete rolebinding/clusterregistry.k8s.io:extension-apiserver-authentication-reader apiservice/v1alpha1.clusterregistry.k8s.io

from cluster-registry.

Looking forward adding the --force option for the init command.

from cluster-registry.

@jianzhangbjz While a --force option doesn't exist for the init subcommand, #192 adds the ability to delete the clusterregistry deployment and it has a --force option as well.

from cluster-registry.

@font Oh, sorry, my misunderstanding. Got it, thanks!

from cluster-registry.

Note that this issue is no longer applicable because of the CRD migration done in #225, which removes crinit and the standalone API server.

from cluster-registry.