From cea3da01a0ae3bd8cc84d3e33c36390b1f7ae4ff Mon Sep 17 00:00:00 2001
From: Lai Jiang <jianglai@google.com>
Date: Fri, 10 Jan 2025 12:25:16 -0500
Subject: [PATCH] Expose Web WHOIS redirects (#2634)

We are required to respond to HTTP(S) requests on port 80/443 on the
same domain where we serve port 43 WHOIS requests. The proxy already
does this by redirecting to the web WHOIS lookup page on the marketing
website.

This PR makes it so that requests to port 80/443 can be routed to the
proxy for redirect.

TESTED=tested on crash and the redirect works.
---
 jetty/kubernetes/nomulus-pubapi.yaml | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/jetty/kubernetes/nomulus-pubapi.yaml b/jetty/kubernetes/nomulus-pubapi.yaml
index 579c7d4cb..9dea8f39d 100644
--- a/jetty/kubernetes/nomulus-pubapi.yaml
+++ b/jetty/kubernetes/nomulus-pubapi.yaml
@@ -38,6 +38,10 @@ spec:
         ports:
         - containerPort: 30001
           name: whois
+        - containerPort: 30010
+          name: http-whois
+        - containerPort: 30011
+          name: https-whois
         resources:
           requests:
             cpu: "500m"
@@ -104,6 +108,12 @@ spec:
   - port: 43
     targetPort: whois
     name: whois
+  - port: 80
+    targetPort: http-whois
+    name: http-whois
+  - port: 443
+    targetPort: https-whois
+    name: https-whois
 ---
 apiVersion: net.gke.io/v1
 kind: ServiceExport