Enable GCE load balancer healthcheck logging

[scarby]

When creating a GCE ingress there appears to be no way to enable logging on the health-checks other than through the gcloud command/console (off by default). This would be a very useful feature when debugging Load Balancer health-checks

(which have been likely been randomly failing for us)

[mvrahden]

Probably related to this one #1598

[scarby]

@mvrahden These two are not related. that one talks about access logging for the load balancer, which is a separate thing to logging for the health-checks

a proposed new spec would be something along the lines of

apiVersion: cloud.google.com/v1beta1
kind: BackendConfig
metadata:
  name: gke-ingress-config
spec:
  healthCheck:
    type: HTTP
    port: 15021
    requestPath: /healthz/ready
    logging:
      enable: true
  logging:
    enable: false

Taking a look through this currently this is read and preserved but not settable.

[swetharepakula]

/kind feature

[dry4ng]

Same request in google IssueTracker: https://issuetracker.google.com/issues/218307146

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[swetharepakula]

We are not planning on supporting this in Ingress and will look to support in the newer Gateway API.

[oliverboehme-ida]

Wow that's a downer 😞