我正在按照 apache pulsar 官方指南在 Kubernetes 中运行 Pulsar 集群 (https://pulsar.apache.org/docs/3.3.x/getting-started-helm/)。当我进入第 1 步时,通过运行提供的脚本创建了安装 Helm Chart 所需的秘密,并尝试运行
helm install \
--values examples/values-minikube.yaml \
--namespace pulsar \
pulsar-mini apache/pulsar
该过程永远卡在那里。
我运行
kubectl get pods
,只发现一个 Pod 处于 CrashLoopBackOff 状态,并且不断失败并重新启动。
NAME READY STATUS RESTARTS AGE
pulsar-mini-kube-prometheu-admission-create-ktpzw 1/1 Running 5 (107s ago) 5m52s
当我查看 Pod 的事件时,它没有显示其他信息。
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 8m21s default-scheduler Successfully assigned pulsar/pulsar-mini-kube-prometheu-admission-create-ktpzw to lima-rancher-desktop
Normal Pulled 4m47s (x5 over 8m21s) kubelet Container image "registry.k8s.io/ingress-nginx/kube-webhook-certgen:v20221220-controller-v1.5.1-58-g787ea74b6" already present on machine
Normal Created 4m47s (x5 over 8m21s) kubelet Created container create
Normal Started 4m47s (x5 over 8m21s) kubelet Started container create
Warning BackOff 3m12s (x13 over 7m20s) kubelet Back-off restarting failed container create in pod pulsar-mini-kube-prometheu-admission-create-ktpzw_pulsar(59d2a69d-c1c2-4d02-92ee-df46e1deb11c)
@Frank 你可以使用这些命令来获取更多日志以更好地了解发生了什么吗???
kubectl logs pulsar-mini-kube-prometheu-admission-create-ktpzw -c create --namespace pulsar
kubectl describe pod pulsar-mini-kube-prometheu-admission-create-ktpzw --namespace pulsar