ChaosMeta installation failed either via helm or manually
Chen-Xintong opened this issue · 0 comments
Chen-Xintong commented
I want to install and test chaosMeta on my cluster, but installation via either helm or kubectl apply fails:
- by Helm
$ helm install my-chaosmeta chaosmeta/chaosmeta --version 0.7.0
Error: INSTALLATION FAILED: Unable to continue with install: ClusterRole "argo-aggregate-to-admin" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "my-chaosmeta"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "default"
- by
kubectl apply
$ kubectl apply -f crds
$ kubectl apply -f templates
The three controller manager always crash:
$ kubectl get all -n chaosmeta
NAME READY STATUS RESTARTS AGE
pod/argo-server-85bfbdf448-995xt 1/1 Running 0 13m
pod/chaosmeta-daemon-9vmxx 1/1 Running 0 14m
pod/chaosmeta-daemon-c568v 1/1 Running 0 14m
pod/chaosmeta-daemon-lkflp 1/1 Running 0 14m
pod/chaosmeta-daemon-tf5wl 1/1 Running 0 14m
pod/chaosmeta-daemon-v64rn 1/1 Running 0 14m
pod/chaosmeta-flow-controller-manager-6bff6d76d-dtkpj 0/1 CrashLoopBackOff 7 (2m51s ago) 14m
pod/chaosmeta-inject-controller-manager-6fffb6d6b4-txqtm 0/1 CrashLoopBackOff 7 (2m21s ago) 14m
pod/chaosmeta-measure-controller-manager-c8d648945-lhwkv 0/1 CrashLoopBackOff 7 (2m28s ago) 14m
pod/chaosmeta-mysql-68795b7bd7-xj4mz 1/1 Running 0 14m
pod/chaosmeta-platform-86d6cb47b9-cl8w4 2/2 Running 0 14m
pod/workflow-controller-64756fd8bb-rmct2 1/1 Running 0 13m
$ kubectl describe po chaosmeta-inject-controller-manager-6fffb6d6b4-txqtm -n chaosmeta
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 15m bin-packing-scheduler Successfully assigned chaosmeta/chaosmeta-inject-controller-manager-6fffb6d6b4-txqtm to ip-10-250-0-79.eu-central-1.compute.internal
Warning FailedMount 15m (x2 over 15m) kubelet MountVolume.SetUp failed for volume "config-volume" : configmap "chaosmeta-inject-config" not found
Normal Pulled 14m kubelet Successfully pulled image "registry.cn-hangzhou.aliyuncs.com/chaosmeta/chaosmeta-inject-controller:v0.1.3" in 10.924s (10.924s including waiting)
Normal Pulled 14m kubelet Successfully pulled image "registry.cn-hangzhou.aliyuncs.com/chaosmeta/chaosmeta-inject-controller:v0.1.3" in 1.973s (1.973s including waiting)
Normal Pulled 14m kubelet Successfully pulled image "registry.cn-hangzhou.aliyuncs.com/chaosmeta/chaosmeta-inject-controller:v0.1.3" in 2.517s (2.517s including waiting)
Normal Pulling 13m (x4 over 15m) kubelet Pulling image "registry.cn-hangzhou.aliyuncs.com/chaosmeta/chaosmeta-inject-controller:v0.1.3"
Normal Created 13m (x4 over 14m) kubelet Created container manager
Normal Started 13m (x4 over 14m) kubelet Started container manager
Normal Pulled 13m kubelet Successfully pulled image "registry.cn-hangzhou.aliyuncs.com/chaosmeta/chaosmeta-inject-controller:v0.1.3" in 2.002s (2.002s including waiting)
Warning BackOff 4m48s (x47 over 14m) kubelet Back-off restarting failed container manager in pod chaosmeta-inject-controller-manager-6fffb6d6b4-txqtm_chaosmeta(901ad105-f29f-49c3-842d-6a6a75434e41)
But I can get the configmap
$ kubectl get cm chaosmeta-inject-config -n chaosmeta
NAME DATA AGE
chaosmeta-inject-config 1 16m
Did I missed some configurations?