kubernetes - Istio 代理崩溃

Question

我使用 kubernetes 和 helm 指令安装了 istio，并注释了一个命名空间以自动注入(inject) istio 代理，但它似乎不能正常工作。代理尝试启动，但由于段错误而不断崩溃。我正在使用 istio 1.0.6。这是代理的日志输出。

[2019-02-27 21:48:50.892][78][warning][upstream] external/envoy/source/common/config/grpc_mux_impl.cc:223] gRPC config for type.googleapis.com/envoy.api.v2.Listener update rejected: Error adding/updating listener 10.16.11.206_8293: unable to read file: /etc/certs/root-cert.pem
[2019-02-27 21:48:50.892][78][warning][config] bazel-out/k8-opt/bin/external/envoy/source/common/config/_virtual_includes/grpc_mux_subscription_lib/common/config/grpc_mux_subscription_impl.h:70] gRPC config for type.googleapis.com/envoy.api.v2.Listener rejected: Error adding/updating listener 10.16.11.206_8293: unable to read file: /etc/certs/root-cert.pem
[2019-02-27 21:48:50.892][78][info][config] external/envoy/source/server/listener_manager_impl.cc:908] all dependencies initialized. starting workers
[2019-02-27 21:48:50.902][83][critical][backtrace] bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:125] Caught Segmentation fault, suspect faulting address 0x0
[2019-02-27 21:48:50.902][83][critical][backtrace] bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:94] Backtrace thr<83> obj</usr/local/bin/envoy> (If unsymbolized, use tools/stack_decode.py):
[2019-02-27 21:48:50.903][83][critical][backtrace] bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:114] thr<83> #0 0x487d8d google::protobuf::internal::ArenaStringPtr::CreateInstanceNoArena()
[2019-02-27 21:48:50.904][83][critical][backtrace] bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:114] thr<83> #1 0x4be9c4 Envoy::Utils::GrpcClientFactoryForCluster()
[2019-02-27 21:48:50.906][83][critical][backtrace] bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:114] thr<83> #2 0x4b8389 Envoy::Tcp::Mixer::Control::Control()
[2019-02-27 21:48:50.907][83][critical][backtrace] bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:114] thr<83> #3 0x4ba7c5 std::_Function_handler<>::_M_invoke()
[2019-02-27 21:48:50.908][83][critical][backtrace] bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:114] thr<83> #4 0x792a15 std::_Function_handler<>::_M_invoke()
[2019-02-27 21:48:50.909][83][critical][backtrace] bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:114] thr<83> #5 0x7c828b Envoy::Event::DispatcherImpl::runPostCallbacks()
[2019-02-27 21:48:50.910][83][critical][backtrace] bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:114] thr<83> #6 0x7c836c Envoy::Event::DispatcherImpl::run()
[2019-02-27 21:48:50.912][83][critical][backtrace] bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:114] thr<83> #7 0x7c4c15 Envoy::Server::WorkerImpl::threadRoutine()
[2019-02-27 21:48:50.913][83][critical][backtrace] bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:114] thr<83> #8 0xb354ad Envoy::Thread::Thread::Thread()::{lambda()#1}::_FUN()
[2019-02-27 21:48:50.913][83][critical][backtrace] bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:104] thr<83> obj</lib/x86_64-linux-gnu/libpthread.so.0>
[2019-02-27 21:48:50.913][83][critical][backtrace] bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:114] thr<83> #9 0x7f2701a296b9 start_thread
[2019-02-27 21:48:50.913][83][critical][backtrace] bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:104] thr<83> obj</lib/x86_64-linux-gnu/libc.so.6>
[2019-02-27 21:48:50.913][83][critical][backtrace] bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:117] thr<83> #10 0x7f270145641c (unknown)
[2019-02-27 21:48:50.913][83][critical][backtrace] bazel-out/k8-opt/bin/external/envoy/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:121] end backtrace thread 83
2019-02-27T21:48:50.923768Z warn    Epoch 0 terminated with an error: signal: segmentation fault
2019-02-27T21:48:50.923870Z warn    Aborted all epochs
2019-02-27T21:48:50.923924Z info    Epoch 0: set retry delay to 25.6s, budget to 2

Answer 1

问题似乎是我的 pod 所在的命名空间中缺少 istio.default secret 。我认为在 istio 基础设施中应该这样做，但似乎没有。将这个 secret 从 istio-system 命名空间复制到我自己的似乎已经解决了这个问题。