From a58af3e371591ed7a7015350512ca46accbf37d6 Mon Sep 17 00:00:00 2001 From: Vincent Ambo Date: Tue, 27 Aug 2019 12:44:37 +0100 Subject: feat(k8s): Configure HTTPS ingress for the blog Uses Google-managed certificates and an Ingress resource to set up an HTTPS load-balancer. This probably won't be the final version as the GKE Ingress is very limited and can not do things like redirect URLs, which I need to decommission the old setup. --- infra/kubernetes/https-lb/ingress.yaml | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 infra/kubernetes/https-lb/ingress.yaml (limited to 'infra/kubernetes/https-lb') diff --git a/infra/kubernetes/https-lb/ingress.yaml b/infra/kubernetes/https-lb/ingress.yaml new file mode 100644 index 000000000000..5afb5f3a48e1 --- /dev/null +++ b/infra/kubernetes/https-lb/ingress.yaml @@ -0,0 +1,15 @@ +# This resource configures the HTTPS load balancer that is used as the +# entrypoint to all HTTPS services running in the cluster. +--- +apiVersion: extensions/v1beta1 +kind: Ingress +metadata: + name: https-ingress + annotations: + networking.gke.io/managed-certificates: tazj-in, www-tazj-in +spec: + # Default traffic is routed to the blog, in case people go to + # peculiar hostnames. + backend: + serviceName: tazblog + servicePort: 8000 -- cgit 1.4.1