我安装了Meshery和 Helm 。
除纤毛外，所有pod均正常
meshery-app-mesh-7d8cb57c85-cfk7j 1/1 Running 0 63m
meshery-cilium-69b4f7d6c5-t9w55 0/1 CrashLoopBackOff 16 (3m16s ago) 63m
meshery-consul-67669c97cc-hxvlz 1/1 Running 0 64m
meshery-istio-687c7ff5bc-bn8mq 1/1 Running 0 63m
meshery-kuma-66f947b988-887hm 1/1 Running 0 63m
meshery-linkerd-854975dcb9-rsgtl 1/1 Running 0 63m
meshery-nginx-sm-55675f57b5-xfpgz 1/1 Running 0 63m字符串
日志显示
level=info msg="Registering workloads with Meshery Server for version v1.14.0-snapshot.4" app=cilium-adapter
panic: interface conversion: error is *fs.PathError, not *errors.Error
goroutine 42 [running]:
github.com/layer5io/meshkit/errors.GetCode({0x278e020?, 0xc0004f7e30?})型
我也查了事件
kubectl get events --field-selector involvedObject.name=meshery-cilium-69b4f7d6c5-t9w55
LAST SEEN TYPE REASON OBJECT MESSAGE
17m Normal Pulling pod/meshery-cilium-69b4f7d6c5-t9w55 Pulling image "layer5/meshery-cilium:stable-latest"
2m44s Warning BackOff pod/meshery-cilium-69b4f7d6c5-t9w55 Back-off restarting failed container meshery-cilium in pod meshery-cilium-69b4f7d6c5-t9w55_default(d7ccd0e8-27e5-4f40-89bc-f8a6dc8fa25a)型
我正在添加来自故障pod的日志事件：
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Pulling 4h25m (x55 over 8h) kubelet Pulling image "layer5/meshery-cilium:stable-latest"
Warning BackOff 3h45m (x1340 over 8h) kubelet Back-off restarting failed container meshery-cilium in pod meshery-cilium-69b4f7d6c5-t9w55_default(d7ccd0e8-27e5-4f40-89bc-f8a6dc8fa25a)
Warning FailedMount 21m (x6 over 21m) kubelet MountVolume.SetUp failed for volume "kube-api-access-tcdml" : object "default"/"kube-root-ca.crt" not registered
Warning NetworkNotReady 20m (x19 over 21m) kubelet network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
Warning BackOff 72s (x82 over 19m) kubelet Back-off restarting failed container meshery-cilium in pod meshery-cilium-69b4f7d6c5-t9w55_default(d7ccd0e8-27e5-4f40-89bc-f8a6dc8fa25a)型
Nginx窗格显示网络问题
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning NodeNotReady 22m node-controller Node is not ready
Warning NetworkNotReady 22m (x18 over 23m) kubelet network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
Warning FailedMount 22m (x7 over 23m) kubelet MountVolume.SetUp failed for volume "kube-api-access-lscv2" : object "default"/"kube-root-ca.crt" not registered型
如何解决此问题？
1条答案
按热度按时间yi0zb3m41#
根据帕特里克Londa的Blog，您的cilium Pod由于
"Back-off restarting failed container"而出现CrashLoopBack off错误，这意味着您的容器在Kubernetes启动后突然终止。1.发生这种情况的原因是，由于活动峰值而导致的临时资源过载。解决此问题的方法是调整periodSeconds或timeoutSeconds，以便为应用程序提供更长的响应时间窗口。
2.有时，内存资源不足会导致这种情况。您可以通过**更改Container资源清单中的“resources：limits”**来增加内存限制，如博客中所示。
请验证上述步骤，并让我知道这是否解决了问题。