fix: use ingress subdomain instead of ipv4 to better reflect usage
Signed-off-by: Devin Buhl <devin@buhl.casa>
This commit is contained in:
5 files changed
+7
-7
No files matched your search
@@ -10,9 +10,9 @@ ingress:
|
||||
- hostname: "${SECRET_DOMAIN}"
|
||||
service: https://ingress-nginx-controller.networking.svc.cluster.local:443
|
||||
originRequest:
|
||||
originServerName: "ipv4.${SECRET_DOMAIN}"
|
||||
originServerName: "ingress.${SECRET_DOMAIN}"
|
||||
- hostname: "*.${SECRET_DOMAIN}"
|
||||
service: https://ingress-nginx-controller.networking.svc.cluster.local:443
|
||||
originRequest:
|
||||
originServerName: "ipv4.${SECRET_DOMAIN}"
|
||||
originServerName: "ingress.${SECRET_DOMAIN}"
|
||||
- service: http_status:404
|
||||
Reference in new issue
Block a user