gpt4 book ai didi

redis - 使用istio时Redis-cluster Helm图表无法完成工作

转载 作者:行者123 更新时间:2023-12-03 06:38:40 25 4
gpt4 key购买 nike

将Bitnami Helm图表用于Redis-Cluster时,会有一个redis-cluster-cluster-create作业。但是,启用istio-injection时,此工作永远不会结束。如果禁用istio-injection,作业将很快结束。有什么解决方案或为什么会出现这种现象?

最佳答案

回答主要问题

there is a redis-cluster-cluster-create job. However, when enabling istio-injection, this job never ends. If I disable istio-injection, the job quickly ends. Any solutions or reason why this phenomenon is happening?


这里的主要问题是,直到所有容器都停止运行,并且Istio sidecar无限期运行,才可以认为作业已完成,尽管您的任务可能已经完成,但整个作业在Kubernetes中不会显示为已完成。
关于这个有 github issue
有一种 workarounds,您可以找到更多解决方法 here

I can change the podAnnotations from Redis-Cluster Helm Chart, and when disabling the istio-injection, the Job doesn't spin up istio-proxy. However, the main job 'cluster-create' job never ends, and eventually fails the the deploy


就像 here

So as a temporary workaround adding sidecar.istio.io/inject: “false” is possible but this disables Istio for any traffic to/from the annotated Pod. As mentioned, we leveraged Kubernetes Jobs for Integration Testing, which meant some tests may need to access the service mesh. Disabling Istio essentially means breaking routing — a show stopper.


因此,它实际上可能在这里不起作用。我建议尝试使用quitquitquit,因为这是最推荐的解决方法。

另外值得检查以下github问题:
  • List of applications incompatible with Istio
  • helm stable/redis does not work with istio sidecar
  • Using Istio with CronJobs
  • Sidecar Containers
  • 关于redis - 使用istio时Redis-cluster Helm图表无法完成工作,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/64476821/

    25 4 0
    Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
    广告合作:1813099741@qq.com 6ren.com