We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug install\helm\hango-gateway\charts\operator-crd\templates\operator-crd.yaml 这个文件中有两个IstioOperator 安装后,在istio-operator中实际处理IstioOperator的顺序可能是hango-gateway在前,hango-istio在后 并且IstioOperator的处理看起来是单线程的
并且gateway-proxy的pod启动依赖istiod,导致等待一段时间后(默认300s,通过istio-operator的WAIT_FOR_RESOURCES_TIMEOUT环境变量配置),直到hango-gateway的IstioOperator状态ERROR后才能启动istiod,此后gateway-proxy的pod才能真正起来
碰到这种情况,只能把hango-gateway的IstioOperator删除后,重新执行helm upgrade
To Reproduce Steps to reproduce the behavior: helm install --namespace hango-system hango-gateway ./helm/hango-gateway/
Expected behavior 有没有办法可以解决这个问题,一次性安装成功? 比如同时并发处理IsitoOperator
Additional context Add any other context about the problem here, e.g.
The text was updated successfully, but these errors were encountered:
wbpcode
No branches or pull requests
Describe the bug
install\helm\hango-gateway\charts\operator-crd\templates\operator-crd.yaml
这个文件中有两个IstioOperator
安装后,在istio-operator中实际处理IstioOperator的顺序可能是hango-gateway在前,hango-istio在后
并且IstioOperator的处理看起来是单线程的
并且gateway-proxy的pod启动依赖istiod,导致等待一段时间后(默认300s,通过istio-operator的WAIT_FOR_RESOURCES_TIMEOUT环境变量配置),直到hango-gateway的IstioOperator状态ERROR后才能启动istiod,此后gateway-proxy的pod才能真正起来
碰到这种情况,只能把hango-gateway的IstioOperator删除后,重新执行helm upgrade
To Reproduce
Steps to reproduce the behavior:
helm install --namespace hango-system hango-gateway ./helm/hango-gateway/
Expected behavior
有没有办法可以解决这个问题,一次性安装成功?
比如同时并发处理IsitoOperator
Additional context
Add any other context about the problem here, e.g.
The text was updated successfully, but these errors were encountered: