繁体   English   中英

如何通过 ConfigMap 使用单个 IP 调试入口控制器连接

[英]How to debug ingress-controller connections with a single IP by ConfigMap

我们正在尝试编辑我们的ingress-nginx.yml以使 ingress-controllers pod 调试来自特定源 IP 的流量 我们的设置是:

  • Kubernetes v1.13
  • 入口控制器 v0.24.1

From NGINX and Kubernetes DOCs it appears there is no very easy way to debug traffic from a single ip (you cannot edit the nginx config directly). 所以,我们想添加debug_connection指令,如下所示:

error_log /path/to/log;
...
events {
    debug_connection 192.168.1.1;
}

正确的做法是通过 ConfigMap 中的 CustomAnnotations + 一个新的入口来启用 CustomAnnotation,所以我们尝试了这个:

kind: ConfigMap
apiVersion: v1
metadata:
  name: nginx-configuration
  namespace: ingress-nginx
  labels:
    app: ingress-nginx
data:
ingress-template: |
    #Creating the custom annotation to make debug_connection on/off
    {if index $.Ingress.Annotations "custom.nginx.org/debug_connection"}
    {$ip := index $.Ingress.Annotations "custom.nginx.org/ip"}
    {end}

    {range $events := .Events}
    events {
      # handling custom.nginx.org/debug_connection
      {if index $.Ingress.Annotations "custom.nginx.org/debug_connection"}
      {end}

和:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: debugenabler
  annotations:
    kubernetes.io/ingress.class: "nginx"
    custom.nginx.org/debug_connection: "on"
    custom.nginx.org/ip: "192.168.1.1"
spec:
  rules:
  - host: "ourhostname"
    http:
      paths:
      - path: /tea
        backend:
          serviceName: tea-svc
          servicePort: 80
      - path: /coffee
        backend:
          serviceName: coffee-svc
          servicePort: 80

我们应用了ingress-nginx.yml没有错误。 我们在 nginx conf 中看到了新行:

location /coffee {

            set $namespace      "test";
            set $ingress_name   "debugenabler";
            set $service_name   "coffee-svc";
            set $service_port   "80";
            set $location_path  "/coffee";

            rewrite_by_lua_block {
                lua_ingress.rewrite({
                    force_ssl_redirect = true,
                    use_port_in_redirects = false,
                })
                balancer.rewrite()

但是关于events块中的 debug_connection 仍然没有:

events {
    multi_accept        on;
    worker_connections  16384;
    use                 epoll;
}

如何在事件上下文中插入 debug_connection?

对于那些可能面临类似挑战的人,我实际上是通过以下方式做到的:

  1. 使用包含debug_connection行的新入口控制器模板文件 ( nginx.tmpl ) 创建一个 ConfigMap(在此处仔细检查您的入口控制器版本,该文件会发生巨大变化)
  2. 创建一个在 Configmap 链接的卷(指定卷和卷挂载)
  3. 创建一个 InitContainer,它在容器启动之前复制 /etc/nginx/template 中的卷内容(这是为了克服可能与权限相关的问题所需要的)。

对于第 2 点和第 3 点,您可以在deploymentpod代码的末尾添加相关代码,我分享一个示例:

     volumes:
        - name: nginxconf2
          configMap:
            name: nginxconf2
            items:
            - key: nginx.tmpl
              path: nginx.tmpl       
      initContainers:
      - name: copy-configs
        image: {{ kubernetes.ingress_nginx.image }}
        volumeMounts:
        - mountPath: /nginx
          name: nginxconf2
        command: ['sh', '-c', 'cp -R /nginx/ /etc/nginx/template/']

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM