Kubernetes Inress:nginx,使用-regex匹配准确的URL路径 [英] Kubernetes Ingress: nginx, use-regex to match exact URL path
本文介绍了Kubernetes Inress:nginx,使用-regex匹配准确的URL路径的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
我有几个Pod,我正在尝试匹配它们各自服务的URL。
请注意,我需要使用nginx.ingress.kubernetes.io/rewrite-target
来解决此问题,而不是nginx.ingress.kubernetes.io/rewrite-target
/api/tile-server/
没有任何正则表达式模式
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
name: ingress-service
annotations:
nginx.ingress.kubernetes.io/ssl-redirect: "true"
nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
nginx.ingress.kubernetes.io/use-regex: "true"
kubernetes.io/ingress.class: "nginx"
cert-manager.io/cluster-issuer: "letsencrypt-prod"
namespace: default
spec:
tls:
- hosts:
- example.com
secretName: tls-secret
rules:
- host: example.com
http:
paths:
- path: /?(.*)
backend:
serviceName: client
servicePort: 80
- path: /api/auth/?(.*)
backend:
serviceName: auth
servicePort: 8000
- path: /api/data/?(.*)
backend:
serviceName: data
servicePort: 8001
- path: /api/tile-server/
backend:
serviceName: tile-server
servicePort: 7800
client
Pod是一款内置在nginx Docker Image中的Reaction应用程序,运行正常nginx.conf
如下所示(如果有帮助)
server {
# listen on port 80
listen 80;
# where the root here
root /usr/share/nginx/html;
# what file to server as index
index index.html index.htm;
location / {
# First attempt to serve request as file, then
# as directory, then fall back to redirecting to index.html
try_files $uri $uri/ /index.html;
}
# Media: images, icons, video, audio, HTC
location ~* .(?:jpg|jpeg|gif|png|ico|cur|gz|svg|svgz|mp4|ogg|ogv|webm|htc)$ {
expires 1M;
access_log off;
add_header Cache-Control "public";
}
# Javascript and CSS files
location ~* .(?:css|js)$ {
try_files $uri =404;
expires 1y;
access_log off;
add_header Cache-Control "public";
}
# Any route containing a file extension (e.g. /devicesfile.js)
location ~ ^.+..+$ {
try_files $uri =404;
}
}
auth
和data
是工作正常的FlaskAPI实例tile-server
也是一个烧瓶舱,但不需要进行任何模式匹配。我需要精确匹配/api/tile-server/
URL
我尝试了以下模式,但失败了:
/api/tile-server/
/api/tile-server/?(.*)
/api/tile-server(/|$)?(.*)
我可以确认Pod/服务在其正确的端口上运行,并且我可以通过节点端口访问它们,但不能通过负载均衡器/域访问它们。
什么模式才能与/api/tile-server/
URL完全匹配?
推荐答案
第一个解决方案-使用重写目标注释为磁贴服务器创建单独的入口对象。这是可行的,因为入口控制器将具有相同主机的入口规则合并在一起,并且单独的入口对象允许每个对象使用不同的注释:
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
name: tile-ingress-service
annotations:
nginx.ingress.kubernetes.io/ssl-redirect: "true"
nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
nginx.ingress.kubernetes.io/rewrite-target: "/$2"
kubernetes.io/ingress.class: "nginx"
cert-manager.io/cluster-issuer: "letsencrypt-prod"
namespace: default
spec:
tls:
- hosts:
- example.com
secretName: tls-secret
rules:
- host: example.com
http:
paths:
- path: /api/tile-server(/|$)(.*)
backend:
serviceName: tile-server
servicePort: 7800
第二个解决方案-重写当前入口以使用重写路径。需要对正则表达式进行一些更改。
注意非捕获组符号:(?:<regex>)
。这允许跳过对这些组的编号,因为我需要所有相关的内容都在第一个组中,才能使其工作,因为rewrite-target: "/$1"
。
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
name: ingress-service
annotations:
nginx.ingress.kubernetes.io/ssl-redirect: "true"
nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
nginx.ingress.kubernetes.io/rewrite-target: "/$1"
kubernetes.io/ingress.class: "nginx"
cert-manager.io/cluster-issuer: "letsencrypt-prod"
namespace: default
spec:
tls:
- hosts:
- example.com
secretName: tls-secret
rules:
- host: example.com
http:
paths:
- path: /(.*)
backend:
serviceName: client
servicePort: 80
- path: /(api/auth(?:/|$).*)
backend:
serviceName: auth
servicePort: 8000
- path: /(api/data(?:/|$).*)
backend:
serviceName: data
servicePort: 8001
- path: /api/tile-server(?:/|$)(.*)
backend:
serviceName: tile-server
servicePort: 7800
以下是重写的工作方式:
- 身份验证服务(同样适用于数据服务)
/api/auth ---> /api/auth
/api/auth/ ---> /api/auth/
/api/auth/xxx ---> /api/auth/xxx
- 磁贴服务器服务:
/api/tile-server ---> /
/api/tile-server/ ---> /
/api/tile-server/xxx ---> /xxx
- 客户端服务
/xxx ---> /xxx
请注意,以下路径将被转发到客户端服务(其中xxx是任意字母数字字符串):
/api/authxxx
/api/dataxxx
/api/tile-serverxxx
如果希望将它们转发给其他/匹配的服务,请在路径中的(?:/|$)
之后添加?
。
这篇关于Kubernetes Inress:nginx,使用-regex匹配准确的URL路径的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
查看全文