1
0
Fork 0

dynk8s: Fix Ingress routing

I guess I thought `defaultBackend` was scoped to the TLS host, but it
appears to be global, across all Ingress resources in the cluster.
Thus, it really doesn't make any sense for any Ingress to have a default
backend, and certainly not the dynk8s provisioner.
dch-webhooks-secrets
Dustin 2022-11-24 11:14:01 -06:00
parent 19ad5023b8
commit 61378e9724
1 changed files with 11 additions and 5 deletions

View File

@ -284,11 +284,17 @@ spec:
tls: tls:
- hosts: - hosts:
- dynk8s-provisioner.pyrocufflink.net - dynk8s-provisioner.pyrocufflink.net
defaultBackend: rules:
service: - host: dynk8s-provisioner.pyrocufflink.net
name: dynk8s-provisioner http:
port: paths:
number: 8000 - path: /
pathType: Prefix
backend:
service:
name: dynk8s-provisioner
port:
name: http
--- ---
apiVersion: v1 apiVersion: v1