Heimdall is a simple gateway for authenticating requests that should come from our IAP-enabled load balancer.
It rejects any request which does not have the expected IAP headers, and performs the work of verifying that those headers are signed by Google.
For some background on using this tool with Ambassador and IAP, check out our blog post.
- Java 10
`mvn package` `docker build -t heimdall:1.0 .` `docker push`
- Google Cloud Account
- Kubernetes Cluster
- Ambassador installed on cluster
- IAP-secured Ingress
- Load balancer health check set to '/load-balancer-health' (and some default backend supplying 200 OK at this route)
k8s/deployment.yamlwith your audience and the location of your built image.
- For more information about your audience, see this page.
kubectl apply -f k8s
Ambassador should start routing requests here before forwarding them to your backend services. You can test this by port-forwarding ambassador, and then making a request without a token. For example:
kubectl port-forward <ambassador-pod> 8080:80& curl -i localhost:8080/load-balancer-health => 200 OK curl -i localhost:8080/heimdall-health => 200 OK curl -i localhost:8080/service-route => HTTP 403 forbidden, as there's no token
Health checks for this service appear somewhat complicated. I'll try to clarify here:
- The health check for the service itself is at "/hemidall-health". It's unlikely any inbound requests are expected to be routed to a service with that resource.
- The "/load-balancer-health" HTTP resource on port 8080 exists for the purposes of Google Cloud's health checks on the load balancer that fronts our ingress. Some notes:
- We add this handler first because we don't expect to auth the request with a token
- This route is explicitly handled by a backend so that it returns 200 OK.
- That route has to be configured in the cloud health checks console. It defaults to "/", which we cannot use for health checks because Heimdall would not be able to differentiate that from a request to "/" for any other host. Nobody should try to utilize that route in their services.
- This will probably eventually want an autoscaling deployment.
- We could publicly host an image.