straight-cartoon-24485
10/16/2023, 2:45 PMdev
and a live
cluster, as two different stacks, inside each of the pulumi programs (so 4 total stacks), but I only have 1 public IP, and so can only use https://www.pulumi.com/registry/packages/kubernetes-cert-manager/ once since I only have 1 domain (managed via gcp CloudDNS)
I think there is a catch-22-situation that I don't know how to reason about yet(?)
I want a valid certificate for both the dev cluster and the live cluster.
Is there a way to tell the live
stack to point its <https://dev.mydomain.com>
to what would be the dev cluster sitting on the same home lab? The idea being to have both <https://myk8sapp.dev.mydomain.com>
and <https://myk8sapp.mydomain.com>
both working. It feels like this will only be possible if I cert-manage letsenrypt on the dev
cluster for the live
cluster...(?)worried-energy-90920
10/16/2023, 3:06 PMstraight-cartoon-24485
10/16/2023, 3:44 PMdev
cluster "match" the live
home-lab cluster as much as possible. I do have a second ISP plugged into the home, so technically, I could get a second domain name to A record to this changing public IP
Or VPS traffic out from dev
to some dummy cloud machine with a static public IP, which moves away from "self"-hosting, though maybe a pragmatic compromise.worried-energy-90920
10/16/2023, 8:00 PMstraight-cartoon-24485
10/16/2023, 8:59 PM