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.
This commit is contained in:
parent
cae99692de
commit
a58af3e371
3 changed files with 29 additions and 0 deletions
15
infra/kubernetes/https-lb/ingress.yaml
Normal file
15
infra/kubernetes/https-lb/ingress.yaml
Normal file
|
|
@ -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
|
||||
Loading…
Add table
Add a link
Reference in a new issue