contrib/federation-experiment/federate: fix ingress bug

This commit fixes an odd ingress bug that appears when the ingress
controller pod is killed and restarted. When that occurs, ingress for
the Tectonic Cluster is broken. The only way to get ingress working
again is to delete the `federation-apiserver` ingress resource created
by the federate tool. Once this is deleted, ingress works again. You can
re-run the federat tool and see ingress continues to work until the
ingress controller pod is restarted. This patch fixes this behavior.

contrib/federation-experiment/federate

@@ -105,11 +105,14 @@ metadata:
  annotations:
  ingress.kubernetes.io/rewrite-target: /
  ingress.kubernetes.io/secure-backends: "true"
- ingress.kubernetes.io/ssl-passthrough: "true"
  kubernetes.io/ingress.class: tectonic
  name: federation-apiserver
  namespace: federation
 spec:
+ tls:
+ - hosts:
+ - $HOST_CONSOLE_DOMAIN
+ secretName: tectonic-ingress-tls-secret
  rules:
  - host: $HOST_CONSOLE_DOMAIN
  http:
@@ -118,13 +121,6 @@ spec:
  serviceName: federation-apiserver
  servicePort: 443
  path: /federation
- - host: federation.$HOST_CONSOLE_DOMAIN
- http:
- paths:
- - backend:
- serviceName: federation-apiserver
- servicePort: 443
- path: /
 EOF
 $KUBECTL apply -f manifests/federation-apiserver-ingress.yaml