Add Hostname to HealthCheckConfig

[AngellusMortis]

Reopen #1046

The docs say the request host header will be set if it is in the pod containers spec.

Request Host header | Host: backend-ip-address | if present in the serving Pod's spec: containers[].readinessProbe.httpGet.httpHeaders

The issue is that this creates a race condition when first creating an ingress if it is created before the pods are deployed (i.e. via Helm). This means if you are deploying an application with strict hostname checking (i.e. Django), your ingress/load balancers will never become healthly unless you delete the ingress and re-add it after the initial deploy.

So it would be nice to actually be able to configure the hostname for the healthcheck as defined in the healthchecks REST API reference

Something like:

apiVersion: cloud.google.com/v1
kind: BackendConfig
metadata:
  name: service-backend-config
spec:
  healthCheck:
    requestPath: /healthcheck/
    host: example.com

I also need this. I don't always have control over what hostname deployment respond on. This is critical and I can do this in the console but not the BackendConfig. There's no technical reason why this couldn't be done.

[jasonwzm]

+1 for this as well.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[AngellusMortis]

/remove-lifecycle stale

[swetharepakula]

/kind feature
/lifecycle frozen

[markbluhm]

+1 for need but for now I am going to try this with my apache server...

The health checks come from the private IP of the load balancer... a 10.0.0.0/8 IP. While it's not ideal, I'm going to just add a virtualhost to my apache server that handles all traffic from 10.0.0.0/8:80 and routes it to whatever host name I wanted it to be ...

Again, not ideal, and could even wind up being a problem if at some point I have an ingress that traffic shows up as coming from ... but I'm just adding the comment here as both a

1. +1 I need this
2. FYI if anyones on Apache, maybe this will work around your problem for now.