argo-cluster-crdview installed twice?

[svanschalkwyk]

kubectl 1.16.0 minikube 1.9.0 git pull 04/02/2020

manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
Error: rendered manifests contain a resource that already exists. Unable to continue with install: existing resource conflict: kind: ClusterRole, namespace: , name: fusion01-argo-cluster-crdview

Waiting up to 10 minutes to see the Fusion API Gateway deployment come online ...

[ian-thebridge-lucidworks]

Hi @svanschalkwyk , That cluster role should be named after the namespace that it is installed into so shouldn't conflict with other resources installed via fusion. Have you had a fusion installed into that namespace before that was not properly deleted with helm? Is there anything else in your cluster that is creating a ClusterRole with the same name?

[svanschalkwyk]

(base) steph@minikube:/nvme/fusion-cloud-native$ k get all --all-namespaces 
NAMESPACE     NAME                                   READY   STATUS    RESTARTS   AGE
kube-system   pod/coredns-66bff467f8-88bnx           1/1     Running   1          20h
kube-system   pod/coredns-66bff467f8-jrft4           1/1     Running   1          20h
kube-system   pod/etcd-minikube                      1/1     Running   1          20h
kube-system   pod/kindnet-9pn7x                      1/1     Running   1          20h
kube-system   pod/kube-apiserver-minikube            1/1     Running   1          20h
kube-system   pod/kube-controller-manager-minikube   1/1     Running   1          20h
kube-system   pod/kube-proxy-57gl6                   1/1     Running   1          20h
kube-system   pod/kube-scheduler-minikube            1/1     Running   1          20h
kube-system   pod/storage-provisioner                1/1     Running   3          20h

NAMESPACE     NAME                 TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)                  AGE
default       service/kubernetes   ClusterIP   10.96.0.1    <none>        443/TCP                  20h
kube-system   service/kube-dns     ClusterIP   10.96.0.10   <none>        53/UDP,53/TCP,9153/TCP   20h

NAMESPACE     NAME                        DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
kube-system   daemonset.apps/kindnet      1         1         1       1            1           <none>                   20h
kube-system   daemonset.apps/kube-proxy   1         1         1       1            1           kubernetes.io/os=linux   20h

NAMESPACE     NAME                      READY   UP-TO-DATE   AVAILABLE   AGE
kube-system   deployment.apps/coredns   2/2     2            2           20h

NAMESPACE     NAME                                 DESIRED   CURRENT   READY   AGE
kube-system   replicaset.apps/coredns-66bff467f8   2         2         2       20h