Serve every tool on deployshed.com instead of nip.io

Harbor, Gitea, Argo CD, Jenkins, Vault, Grafana and vmui now answer on
their deployshed.com names alone. Each was already serving both while the
move was proved out; this removes the nip.io half.

The dual-hostname workarounds go with it. Jenkins' secondaryingress existed
only because its chart's primary ingress takes one hostName and a
certificate could not span both names — the real domain moves onto the
primary with jenkins-tls, which it already holds. Argo CD gets extraTls
rather than ingress.tls, because the boolean hardcodes secretName
argocd-server-tls and would request a second certificate for a name that
already has a valid one in argocd-deployshed-tls.

Harbor also changes in two ways beyond the hostname:

  - externalURL moves to https://harbor.infra.deployshed.com. Harbor hands
    this to docker clients in its own API responses and builds the push
    commands shown in its UI from it, so a stale value is what makes a
    correctly-configured registry still advertise the old address.

  - updateStrategy is now Recreate. Its jobservice and registry volumes are
    standard-rwo (ReadWriteOnce), and a RollingUpdate starts the new pod
    before the old one releases the disk, so the replacement hangs forever
    on Multi-Attach. The cluster was sitting in exactly that state, old pods
    serving while new ones stayed in ContainerCreating. The chart's own
    comment on this value recommends Recreate when RWM is unavailable. The
    cost is a brief outage during upgrades, which beats a rollout that
    cannot complete.

The private registry CA is not removed yet. Apps deployed before this move
recorded nip.io image references that only change when each is rebuilt, so
the old hostname stays served by a standalone Ingress until then.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LEsTefWWifp4ikvhHF5s6N

helm-overrides/gke-toolshed-prd-usc1/jenkins/custom-values.yaml

@@ -55,27 +55,23 @@ jenkins:
       userKey: jenkins-admin-user
       passwordKey: jenkins-admin-password
 
-    ingress:
-      enabled: true
-      hostName: "jenkins.35.238.248.203.nip.io"
-      ingressClassName: contour
+    # One hostname, on the primary ingress, with its certificate.
+    #
     # This chart's primary ingress supports exactly one hostName — no
-    # extraHosts like argo-cd. secondaryingress renders a whole second
-    # Ingress object at the same backend, which is the supported way to get
-    # a second hostname here.
+    # extraHosts like argo-cd — so while nip.io was also served, the real
+    # domain lived in a whole second Ingress object (secondaryingress). That
+    # was the only way to keep the certificate clean, since a certificate
+    # covering both names is impossible: Let's Encrypt cannot issue for
+    # nip.io. With nip.io gone there is one name, so the second object is
+    # gone with it and the certificate moves onto the primary.
     #
-    # paths must be set explicitly: the template renders zero routes if left
-    # at the chart's own default of [], unlike the primary ingress, and the
-    # hostname would then answer nothing at all.
-    #
-    # Being a separate Ingress object is what makes the certificate clean —
-    # it covers this hostname alone, with no nip.io name to drag in.
-    secondaryingress:
+    # controller.ingress.tls is a LIST here, not a boolean, taking an
+    # explicit secretName — so jenkins-tls, already issued for this exact
+    # hostname by the secondary ingress, is adopted rather than reissued.
+    ingress:
       enabled: true
       hostName: "jenkins.infra.deployshed.com"
       ingressClassName: contour
-      paths:
-        - /
       annotations:
         cert-manager.io/cluster-issuer: letsencrypt-prod
       tls: