[英]linkerd: crashloopbackoff kubernetes pod error while setting failure accrual
Configured my yml with failure accrual circuit breaking, with below config as reference. 为我的yml配置了故障应计故障电路,并使用以下配置作为参考。 https://github.com/linkerd/linkerd-examples/blob/master/failure-accrual/linkerd.yml https://github.com/linkerd/linkerd-examples/blob/master/failure-accrual/linkerd.yml
client:
failureAccrual:
kind: io.l5d.consecutiveFailures
failures: 5
backoff:
kind: constant
ms: 10000
After applying the changes, I see the pods in crashloopbackoff state. 应用更改后,我看到Pod处于crashloopbackoff状态。
kubectl apply -f ./linkerd-fa.yml
Crashloopbackoff
means that the process is failing to start. Crashloopbackoff
表示该进程无法启动。 If you use kubectl logs pod/$POD_ID l5d
, you should see an error message. 如果您使用kubectl logs pod/$POD_ID l5d
,则应该看到错误消息。 I'm guessing there's a formatting issue with your configuration that is causing linkerd to error out during startup. 我猜您的配置存在格式化问题,导致启动时linkerd错误。
Linkerd provides failure accrual by default as part of each of your client configurations. 默认情况下,Linkerd作为每个客户端配置的一部分提供了应计失败。 The default failure accrual configuration is 5 consecutive failures, which is also what you've pasted in the YAML snippet with your question. 默认的失败应计配置是5次连续失败,这也是您在问题中粘贴到YAML代码段中的内容。 So in this case you could omit the failureAccrual setting altogether from your config and the behavior will be the same. 因此,在这种情况下,您可以从配置中完全忽略failureAccrual设置,其行为将是相同的。
我认为您应该删除Pod,它是Crashloopbackoff ,然后运行kubectl get pods
。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.