From 61378e972404da2ebced61ad44c989da7cf9f475 Mon Sep 17 00:00:00 2001
From: "Dustin C. Hatch" <dustin@hatch.name>
Date: Thu, 24 Nov 2022 11:14:01 -0600
Subject: [PATCH] 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.
---
 dynk8s-provisioner/dynk8s-provisioner.yaml | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/dynk8s-provisioner/dynk8s-provisioner.yaml b/dynk8s-provisioner/dynk8s-provisioner.yaml
index 280de7d..8853e62 100644
--- a/dynk8s-provisioner/dynk8s-provisioner.yaml
+++ b/dynk8s-provisioner/dynk8s-provisioner.yaml
@@ -284,11 +284,17 @@ spec:
   tls:
   - hosts:
     - dynk8s-provisioner.pyrocufflink.net
-  defaultBackend:
-    service:
-      name: dynk8s-provisioner
-      port:
-        number: 8000
+  rules:
+  - host: dynk8s-provisioner.pyrocufflink.net
+    http:
+      paths:
+      - path: /
+        pathType: Prefix
+        backend:
+          service:
+            name: dynk8s-provisioner
+            port:
+              name: http
 
 ---
 apiVersion: v1