Kubernetes Ingress 后端子路径

Kubernetes Ingress backend subpath

是否可以通过任何方式将主机路径重定向到后端的子路径?类似于 subPaths 处理卷的方式。

入口看起来像这样:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: jupyter-notebook-ingress
  annotations:
    kubernetes.io/ingress.class: nginx
spec:
  rules:
    - host: jptrntbk.MYDOMAIN.com
      http:
        paths:
          - path: /
            backend:
              serviceName: jupyter-notebook-service
              servicePort: 8888
              subPath: /lab

导航到 jptrntbk.MYDOMAIN.com 将在后端重定向到 /lab,所有其他父路径都不可用。

创建带有 app-root 注释的 Ingress 规则:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    nginx.ingress.kubernetes.io/app-root: /app1
  name: approot
  namespace: default
spec:
  rules:
  - host: approot.bar.com
    http:
      paths:
      - backend:
          serviceName: http-svc
          servicePort: 80
        path: /

检查重写是否正常工作

$ curl -I -k http://approot.bar.com/
HTTP/1.1 302 Moved Temporarily
Server: nginx/1.11.10
Date: Mon, 13 Mar 2017 14:57:15 GMT
Content-Type: text/html
Content-Length: 162
Location: http://stickyingress.example.com/app1
Connection: keep-alive

或者您可以创建带有重写注释的 Ingress 规则:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /
  name: rewrite
  namespace: default
spec:
  rules:
  - host: rewrite.bar.com
    http:
      paths:
      - backend:
          serviceName: http-svc
          servicePort: 80
        path: /something(/|$)(.*)

在此入口定义中,(.*) 捕获的任何字符都将分配给占位符 </code>,然后用作 <code>rewrite-target 注释中的参数。

例如,上面的入口定义将导致以下重写:- rewrite.bar.com/something 重写为 rewrite.bar.com/ - rewrite.bar.com/something/ 重写为 rewrite.bar.com/ - rewrite.bar.com/something/new重写为 rewrite.bar.com/new