Document/Reference - Static IP setup somewhere (GKE)

[consideRatio]

The configuring-domain-name-static-ip documentation is very relevant to users that would like to establish a fixed IP to point their domain name to.

Apparently it will be quite easy for users on GKE.

1. Create a named reserved static globally available external ip address using the gcloud tool - a one liner.
2. Set an annotation on the ingress object through config.yaml

ingress:
  annotations:
    - kubernetes.io/ingress.global-static-ip-name: ip-addr-name

[consideRatio]

Well this was a bit more complicated than I thought...

There are two templates with ingress objects within the z2jh helm chart, but the only one that is in use by me with a letsencrypt setup is the one in templates/proxy/autohttps/ingress-internal.yaml. There is also another ingress object created by the autohttps deployment, hmm...

What is the object that I need to annotate?

$ kubectl get svc
NAME              TYPE           CLUSTER-IP    EXTERNAL-IP    PORT(S)                      AGE
hub               ClusterIP      10.0.8.147    <none>         8081/TCP                     34m
kube-lego-nginx   ClusterIP      10.0.2.44     <none>         8080/TCP                     33m
proxy-api         ClusterIP      10.0.12.64    <none>         8001/TCP                     34m
proxy-http        ClusterIP      10.0.14.242   <none>         8000/TCP                     34m
proxy-public      LoadBalancer   10.0.2.156    35.204.7.244   80:31416/TCP,443:30456/TCP   34m

$ kubectl get ingress
NAME                  HOSTS             ADDRESS          PORTS     AGE
jupyterhub-internal   dsp.allting.com   35.204.113.143   80, 443   32m
kube-lego-nginx       dsp.allting.com   35.204.113.143   80        31m

[clkao]

Note that this will currently fail with cert-manager based tls due to a bug in ingress-gce: cert-manager/cert-manager#606

PR for the fix: kubernetes/ingress-gce#388

[consideRatio]

Thanks for the headsup @clkao!

What ive done that works (step 2a in guide linked above), but still confused about regional/global address difference, written from memory on mobile

# reserve an ip...
gcloud compute addresses create my-regional-ip

# copy the ip reserved for you...
gcloud compute addresses describe my-regional-ip

# add it to config.yaml at...
proxy:
  service:
    loadBalancerIP: 123.123.123.123

Current understanding of regional ip/global ip: loadBalancers are regional, and is only allowed to be assigned a regional IP for some high level networking reason. A regional IP is still an external IP accessible to the internet users though. The downsidebis that one must create a global IP if one wants to span multiple regions later with a loadbalancer that passes traffic onwards to various regions - but this overkill for most use cases on a z2jh deployment.

[consideRatio]

Closing in favor of #748