如何解决特使代理 HTTP 503 连接本地重置错误
我在负载平衡应用程序的容器中使用特使代理作为反向代理。我们最近发生了网络中断,导致特使代理向下游客户端返回 503。通常,当网络中断恢复时,Envoy 代理将能够再次正常连接到我们的上游服务器,每个人都很高兴。
但是,在网络中断恢复后,除非我重新启动容器,否则下游客户端仍会收到带有 LR 响应标志的 HTTP 503。我错过了什么吗?有人能指出我应该如何解决这个问题的正确方向吗?
admin:
access_log_path: /tmp/admin_access.log
address:
socket_address:
protocol: TCP
address: 0.0.0.0
port_value: 9901
static_resources:
listeners:
- name: listener_0
address:
socket_address:
protocol: TCP
address: 0.0.0.0
port_value: 10000
filter_chains:
- filters:
- name: envoy.filters.network.http_connection_manager
typed_config:
"@type": type.googleapis.com/envoy.config.filter.network.http_connection_manager.v2.HttpConnectionManager
stat_prefix: ingress_http
server_name: none
route_config:
name: local_route
response_headers_to_remove:
- x-envoy-upstream-service-time
virtual_hosts:
- name: local_service
domains: ["*"]
routes:
- match:
prefix: "/"
route:
host_rewrite: api.example.com
cluster: service_api
http_filters:
- name: envoy.filters.http.router
access_log:
- name: envoy.access_loggers.file
filter:
not_health_check_filter: {}
config:
path: "/dev/stdout"
clusters:
- name: service_api
connect_timeout: 30s
type: LOGICAL_DNS
dns_resolvers:
socket_address:
address: 127.0.0.1
port_value: 53
# Comment out the following line to test on v6 networks
dns_lookup_family: V4_ONLY
lb_policy: ROUND_ROBIN
upstream_connection_options:
tcp_keepalive: {}
load_assignment:
cluster_name: service_api
endpoints:
- lb_endpoints:
- endpoint:
address:
socket_address:
address: api.example.com
port_value: 443
transport_socket:
name: envoy.transport_sockets.tls
typed_config:
"@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.UpstreamTlsContext
任何指针将不胜感激。
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。