将 Envoy 设置为 Docker 容器内的反向代理

如何解决将 Envoy 设置为 Docker 容器内的反向代理

我正在尝试了解更多关于 Envoy(使用 Docker 映像)并将其设置为反向代理的信息。

Requests → Docker container running Envoy → Proxy to a different server based on the request.

我遇到了解决代理地址的问题。这是我访问 localhost:8080 时看到的内容。

upstream connect error or disconnect/reset before headers. reset reason: connection failure

特使配置

Dockerfile

FROM envoyproxy/envoy:v1.18.3
COPY envoy-custom.yaml /etc/envoy/envoy.yaml
RUN chmod go+r /etc/envoy/envoy.yaml

Envoy 配置 envoy-custom.yaml,使用 example here 的简化版本。它正在侦听端口 8080,并尝试代理到内部服务器。为简单起见,它目前设置为代理所有请求。

static_resources:
  listeners:
    - name: listener_0
      address:
        socket_address:
          address: 0.0.0.0
          port_value: 8080
      filter_chains:
        - filters:
            - name: envoy.http_connection_manager
              typed_config:
                "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
                stat_prefix: ingress_http
                route_config:
                  name: local_route
                  virtual_hosts:
                    - name: gateway
                      domains:
                        - "*"
                      routes:
                        - match:
                            prefix: "/"
                          route:
                            cluster: targetCluster
                http_filters:
                  - name: envoy.filters.http.router
                    typed_config: {}

  clusters:
    - name: targetCluster
      connect_timeout: 0.25s
      type: LOGICAL_DNS
      lb_policy: ROUND_ROBIN
      load_assignment:
        cluster_name: frontend
        endpoints:
          - lb_endpoints:
              - endpoint:
                  address:
                    socket_address:
                      # address: host.docker.internal
                      # address: some-address-inside-a-corp-network
                      # For the purposes of this post,proxying 
                      # to Google
                      address: google.com
                      port_value: 80

Envoy 配置似乎符合 V3。

$ docker run --rm \
  -v (pwd)/envoy.custom.yaml:/my-envoy-config.yaml \
  envoyproxy/envoy:v1.18.3 \
  --mode validate \
  -c my-envoy-config.yaml


[2021-05-20 17:30:35.544][1][info][main] [source/server/server.cc:667] runtime: layers:
  - name: base
    static_layer:
      {}
  - name: admin
    admin_layer:
      {}
[2021-05-20 17:30:35.544][1][info][config] [source/server/configuration_impl.cc:128] loading tracing configuration
[2021-05-20 17:30:35.544][1][info][config] [source/server/configuration_impl.cc:88] loading 0 static secret(s)
[2021-05-20 17:30:35.544][1][info][config] [source/server/configuration_impl.cc:94] loading 1 cluster(s)
[2021-05-20 17:30:35.545][1][info][config] [source/server/configuration_impl.cc:98] loading 1 listener(s)
configuration 'my-envoy-config.yaml' OK
[2021-05-20 17:30:35.547][1][info][config] [source/server/configuration_impl.cc:110] loading stats configuration

Envoy 登录调试模式:

...
[2021-05-20 17:15:02.991][1][debug][upstream] [source/common/upstream/upstream_impl.cc:279] transport socket match,socket default selected for host with address [2607:f8b0:4007:804::200e]:80
[2021-05-20 17:15:02.991][1][debug][upstream] [source/common/upstream/strict_dns_cluster.cc:170] DNS refresh rate reset for google.com,refresh rate 5000 ms
[2021-05-20 17:15:07.960][1][debug][upstream] [source/common/upstream/upstream_impl.cc:279] transport socket match,socket default selected for host with address [2607:f8b0:4007:804::200e]:80
[2021-05-20 17:15:07.960][1][debug][upstream] [source/common/upstream/strict_dns_cluster.cc:170] DNS refresh rate reset for google.com,refresh rate 5000 ms
...

就其价值而言,我能够使用 Nginx 成功实现代理,使用这些配置。

nginx.conf

server {
    listen       8080;
    server_name  0.0.0.0;

    location / {
      # Testing if proxying is working locally; seems to be
      # proxy_pass http://host.docker.internal:9090;

      # Testing if proxying to a corp server is working; seems to be
      # proxy_pass some-address-inside-a-corp-network

      # For the purposes of this post,proxying to Google
      proxy_pass https://www.google.com;
    }
}

用于设置 Nginx 的 Dockerfile

FROM nginx:latest

COPY nginx.conf /etc/nginx/conf.d/default.conf

问题

我的配置中是否遗漏了一些东西,这会阻止 Envoy 进行代理?

解决方法

从你贴出的日志来看上游地址是在ip v6中解析的,尝试将其限制在https://www.envoyproxy.io/docs/envoy/v1.18.3/api-v3/config/cluster/v3/cluster.proto#enum-config-cluster-v3-cluster-dnslookupfamily中的v4。另外,不知道这是否是一个因素,但您将 Nginx 代理到 Google.com 的 443 端口,而不是像 Envoy 配置中的 80 端口。

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 <select id="xxx"> SELECT di.id, di.name, di.work_type, di.updated... <where> <if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 <property name="dynamic.classpath" value="tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams['font.sans-serif'] = ['SimHei'] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -> systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping("/hires") public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate<String
使用vite构建项目报错 C:\Users\ychen\work>npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-