Split chime Ingress, to allow two certs

Splits chime Ingress into two resources, so that cert-manager
will create two separate TLS certificates.

This allows more flexibility with external DNS records.

Author: asauber

k8s/app.yaml

@@ -63,12 +63,12 @@ metadata:
   annotations:
     kubernetes.io/ingress.class: nginx
     certmanager.k8s.io/cluster-issuer: letsencrypt-prod
+    # allow requests larger than 1MiB
     nginx.ingress.kubernetes.io/proxy-body-size: "0"
 spec:
   tls:
   - hosts:
-    # - penn-chime.phl.io
-    - lke.penn-chime.phl.io
+    - penn-chime.phl.io
     secretName: tls-secret
   rules:
   - host: penn-chime.phl.io
@@ -78,6 +78,25 @@ spec:
         backend:
           serviceName: chime
           servicePort: 80
+
+---
+
+apiVersion: extensions/v1beta1
+kind: Ingress
+metadata:
+  name: chime-alt
+  namespace: chime
+  annotations:
+    kubernetes.io/ingress.class: nginx
+    certmanager.k8s.io/cluster-issuer: letsencrypt-prod
+    # allow requests larger than 1MiB
+    nginx.ingress.kubernetes.io/proxy-body-size: "0"
+spec:
+  tls:
+  - hosts:
+    - lke.penn-chime.phl.io
+    secretName: tls-chime-alt
+  rules:
   - host: lke.penn-chime.phl.io
     http:
       paths:
@@ -87,7 +106,6 @@ spec:
           servicePort: 80
 
 ---
-
 apiVersion: extensions/v1beta1
 kind: Ingress
 metadata: