Kubernetes 由于死锁，播客未准备就绪

我正在使用openshift群集部署我的k8s操作符。我不是从操作员中心手动部署操作员。我成功地部署了操作员。但是当我试图通过操作员进行部署时，它会给我以下错误

如果我执行“kubectl日志命令”：

---

看起来我的豆荚因为这把锁而一直没有准备好，有什么解决办法吗？

就像上面说的，其他人有领导人选举锁。您配置了哪种选举模式？将在初始化Manager对象的代码中。

{“level”：“info”，“ts”：1585406191.5270786，“logger”：“leader”，“msg”：“Found existing lock”，“LockOwner”：“apim-operator-b6446674d-56zp2”}

这是告诉您pod

“apim-operator-b6446674d-56zp2”

拥有锁。检查podI删除被驱逐吊舱的日志。它解决了这个错误，谢谢：）正如它所说，其他人拥有领导人选举锁。您配置了哪种选举模式？将在初始化Manager对象的代码中。

{“level”：“info”，“ts”：1585406191.5270786，“logger”：“leader”，“msg”：“Found existing lock”，“LockOwner”：“apim-operator-b6446674d-56zp2”}

这是告诉您pod

“apim-operator-b6446674d-56zp2”

拥有锁。检查podI删除被驱逐吊舱的日志。它解决了错误，谢谢：）

{"level":"info","ts":1585406191.404172,"logger":"cmd","msg":"Go Version: go1.13"}
{"level":"info","ts":1585406191.404281,"logger":"cmd","msg":"Go OS/Arch: linux/amd64"}
{"level":"info","ts":1585406191.4042957,"logger":"cmd","msg":"Version of operator-sdk: v0.7.0+git"}
{"level":"info","ts":1585406191.4049966,"logger":"leader","msg":"Trying to become the leader."}
{"level":"info","ts":1585406191.5270786,"logger":"leader","msg":"Found existing lock","LockOwner":"apim-operator-b6446674d-56zp2"}
{"level":"info","ts":1585406191.5332227,"logger":"leader","msg":"Not the leader. Waiting."}
{"level":"info","ts":1585406192.661973,"logger":"leader","msg":"Not the leader. Waiting."}