无法获取资产以服务于 ingress-nginx 后面的遗留 PHP 应用程序

Question

所以这就是我想做的，因为我的 /admin/v2 路线继续正常工作...但是，找不到遗留的静态资产 (<= 2013) PHP 在 /admin 路线申请：

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: "nginx"
    cert-manager.io/cluster-issuer: "letsencrypt-dev"
    nginx.ingress.kubernetes.io/ssl-redirect: "true"
  name: ingress-dev
  namespace: dev
spec:
  tls:
    - hosts:
        - localhost
      secretName: tls-localhost-dev
  rules:
    - host: localhost
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: client-cluster-ip-service-dev
                port:
                  number: 3000
          - path: /admin
            pathType: Prefix
            backend:
              service:
                name: admin-cluster-ip-service-dev
                port:
                  number: 4000
          - path: /admin/v2
            pathType: Prefix
            backend:
              service:
                name: admin-v2-cluster-ip-service-dev
                port:
                  number: 4001
          - path: /api
            pathType: Prefix
            backend:
              service:
                name: api-cluster-ip-service-dev
                port:
                  number: 5000

也就是说，我可以通过以下方式正确加载资产，但是 /admin/v2 路线（或 /admin-v2）不再有效，而是转到 /admin路线：

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: "nginx"
    cert-manager.io/cluster-issuer: "letsencrypt-dev"
    nginx.ingress.kubernetes.io/ssl-redirect: "true"
    nginx.ingress.kubernetes.io/add-base-url: "true"
    nginx.ingress.kubernetes.io/rewrite-target: /
    nginx.ingress.kubernetes.io/proxy-body-size: "0"
    nginx.org/client-max-body-size: "500m"
    nginx.ingress.kubernetes.io/use-regex: "true"
    nginx.ingress.kubernetes.io/configuration-snippet: |
      rewrite ^(/admin)$ / permanent;
  name: ingress-dev
  namespace: dev
spec:
  tls:
    - hosts:
        - localhost
      secretName: tls-localhost-dev
  rules:
    - host: localhost
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: client-cluster-ip-service-dev
                port:
                  number: 3000
          - path: /admin/?(.*)
            pathType: Prefix
            backend:
              service:
                name: admin-cluster-ip-service-dev
                port:
                  number: 4000
          - path: /admin/v2
            pathType: Prefix
            backend:
              service:
                name: admin-v2-cluster-ip-service-dev
                port:
                  number: 4001
          - path: /api
            pathType: Prefix
            backend:
              service:
                name: api-cluster-ip-service-dev
                port:
                  number: 5000

所以我想保留第一个配置，但也希望为 /admin 正确加载静态资产，我不知道如何做到这一点。

ingress-nginx 到 /admin 的流量应该转到 Pod 中的 nginx 运行。我认为解决方案可能必须来自那里。这是它的配置：

server {
  listen 4000;
  # rewrite ^([^.]*[^/])$ / permanent;
  root   /usr/share/nginx/html/src;

  include /etc/nginx/default.d/*.conf;

  index app.php index.php index.html index.htm;

  client_max_body_size 500m;

  location / {
    try_files $uri $uri/ /index.php$is_args$args;
  }

  location ~ [^/]\.php(/|$) {
    fastcgi_split_path_info ^(.+?\.php)(/.*)$;
    # Mitigate https://httpoxy.org/ vulnerabilities
    fastcgi_param HTTP_PROXY "";
    fastcgi_pass 127.0.0.1:9000;
    fastcgi_index index.php;
    include fastcgi.conf;
  }
}

此外，这是在 index.tbs HTML 模板文件中引用资产的方式，我已尝试将 admin/ 附加到该文件，但这只是URL localhost/admin/admin/css/default.css 当您在“元素”选项卡中检查它时：

<link rel="STYLESHEET" type="text/css" href="css/portal.css" />
<link rel="STYLESHEET" type="text/css" href="css/default.css" />

关于如何解决这个问题的建议？

澄清一下，当我查看它尝试提供的 .css 时，它只是为网站编译的 HTML。

编辑：

一点点进步...我在 nginx.conf 中添加了以下内容：

  location / {
    try_files $uri $uri/ /index.php$is_args$args;
    rewrite  ^/admin/(.*) / break;
  }

现在，当我降落在 localhost/admin 路线时，它正在正确地提供 CSS 资产，但随后我登录，这将我定向到 localhost/admin/index.php，它显示“找不到文件”。所以我需要以某种方式从中排除 .php。

Answer 1

好的，解决了。也许不是最佳实践...

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: "nginx"
    cert-manager.io/cluster-issuer: "letsencrypt-dev"
    nginx.ingress.kubernetes.io/ssl-redirect: "true"

    # this is apparently needed otherwise it doesn't serve the assets
    # trying to do this in nginx.conf, just automatically re-routes to
    # localhost:4000/admin for some reason
    nginx.ingress.kubernetes.io/configuration-snippet: |
      rewrite ^(/admin)$ / permanent;
  name: ingress-dev
  namespace: dev
spec:
  tls:
    - hosts:
        - localhost
      secretName: tls-localhost-dev
  rules:
    - host: localhost
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: client-cluster-ip-service-dev
                port:
                  number: 3000
          - path: /admin
            pathType: Prefix
            backend:
              service:
                name: admin-cluster-ip-service-dev
                port:
                  number: 4000
          - path: /admin/v2
            pathType: Prefix
            backend:
              service:
                name: admin-v2-cluster-ip-service-dev
                port:
                  number: 4001
          - path: /api
            pathType: Prefix
            backend:
              service:
                name: api-cluster-ip-service-dev
                port:
                  number: 5000

server {
  listen 4000;
  root   /usr/share/nginx/html/src;

  include /etc/nginx/default.d/*.conf;

  index app.php index.php index.html index.htm;

  client_max_body_size 500m;

  location / {
    try_files $uri $uri/ /index.php$is_args$args;
    rewrite  ^/admin/?(.*) / break;
  }

  location ~ [^/]\.php(/|$) {
    fastcgi_split_path_info ^(.+?\.php)(/.*)$;
    rewrite  ^/admin/?(.*) / break;
    fastcgi_param HTTP_PROXY "";
    fastcgi_pass 127.0.0.1:9000;
    fastcgi_index index.php;
    include fastcgi.conf;
  }
}

无法获取资产以服务于 ingress-nginx 后面的遗留 PHP 应用程序

Trouble getting assets to serve for legacy PHP application behind ingress-nginx

php

nginx

kubernetes

nginx-ingress