时间戳

首页 > 解决方案 > 来自 kubernetes pod 的 Squid 代理连接

azure - 来自 kubernetes pod 的 Squid 代理连接

问题描述

我能够在 Azure 中成功设置代理服务器并在我的浏览器上使用它进行验证。我有一个在 Kubernetes pod 上运行的应用程序，我已将代理 url 作为环境变量传递给该 pod。pod 被配置为 daemonSet。一旦我输入代理网址 - 以下是我得到的错误： 

`/usr/lib/ruby/2.3.0/net/http/response.rb:120:in `error!': 503 "Service Unavailable" (Net::HTTPFatalError)
    from /usr/lib/ruby/2.3.0/net/http/response.rb:129:in `value'
    from /usr/lib/ruby/2.3.0/net/http.rb:920:in `connect'
    from /usr/lib/ruby/2.3.0/net/http.rb:863:in `do_start'
    from /usr/lib/ruby/2.3.0/net/http.rb:852:in `start'
    from /var/lib/gems/2.3.0/gems/rest-client-2.0.2/lib/restclient/request.rb:715:in `transmit'
    from /var/lib/gems/2.3.0/gems/rest-client-2.0.2/lib/restclient/request.rb:145:in `execute'
    from /var/lib/gems/2.3.0/gems/rest-client-2.0.2/lib/restclient/request.rb:52:in `execute'
    from /var/lib/gems/2.3.0/gems/rest-client-2.0.2/lib/restclient/resource.rb:51:in `get'
    from /var/lib/gems/2.3.0/gems/kubeclient-1.1.4/lib/kubeclient/common.rb:328:in `block in api'
    from /var/lib/gems/2.3.0/gems/kubeclient-1.1.4/lib/kubeclient/common.rb:58:in `handle_exception'
    from /var/lib/gems/2.3.0/gems/kubeclient-1.1.4/lib/kubeclient/common.rb:327:in `api'
    from /var/lib/gems/2.3.0/gems/kubeclient-1.1.4/lib/kubeclient/common.rb:322:in `api_valid?'
    from /var/lib/gems/2.3.0/gems/fluent-plugin-kubernetes_metadata_filter-2.1.2/lib/fluent/plugin/filter_kubernetes_metadata.rb:234:in `configure'
    from /var/lib/gems/2.3.0/gems/fluentd-1.2.0/lib/fluent/plugin.rb:164:in `configure'
    from /var/lib/gems/2.3.0/gems/fluentd-1.2.0/lib/fluent/agent.rb:152:in `add_filter'
    from /var/lib/gems/2.3.0/gems/fluentd-1.2.0/lib/fluent/agent.rb:70:in `block in configure'
    from /var/lib/gems/2.3.0/gems/fluentd-1.2.0/lib/fluent/agent.rb:64:in `each'
    from /var/lib/gems/2.3.0/gems/fluentd-1.2.0/lib/fluent/agent.rb:64:in `configure'
    from /var/lib/gems/2.3.0/gems/fluentd-1.2.0/lib/fluent/root_agent.rb:112:in `configure'
    from /var/lib/gems/2.3.0/gems/fluentd-1.2.0/lib/fluent/engine.rb:131:in `configure'
    from /var/lib/gems/2.3.0/gems/fluentd-1.2.0/lib/fluent/engine.rb:96:in `run_configure'
    from /var/lib/gems/2.3.0/gems/fluentd-1.2.0/lib/fluent/supervisor.rb:795:in `run_configure'
    from /var/lib/gems/2.3.0/gems/fluentd-1.2.0/lib/fluent/supervisor.rb:579:in `dry_run'
    from /var/lib/gems/2.3.0/gems/fluentd-1.2.0/lib/fluent/supervisor.rb:597:in `supervise'
    from /var/lib/gems/2.3.0/gems/fluentd-1.2.0/lib/fluent/supervisor.rb:502:in `run_supervisor'
    from /var/lib/gems/2.3.0/gems/fluentd-1.2.0/lib/fluent/command/fluentd.rb:310:in `<top (required)>'
    from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /var/lib/gems/2.3.0/gems/fluentd-1.2.0/bin/fluentd:8:in `<top (required)>'
    from /usr/local/bin/fluentd:22:in `load'
    from /usr/local/bin/fluentd:22:in `<main>'

此时的 pod 没有以CrashLoopBackOff.

任何帮助都会很棒。此外，如果需要任何其他信息 - 我会补充。请提一下。

标签： azurekubernetessquidkubernetes-podazure-aks

解决方案

推荐阅读