Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to implement content-based health check for GKE ingress #2468

Open
raweber42 opened this issue Feb 15, 2024 · 6 comments
Open

How to implement content-based health check for GKE ingress #2468

raweber42 opened this issue Feb 15, 2024 · 6 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@raweber42
Copy link

I want to implement a content-based health check for my GKE ingress. These kinds of health checks are usually specified in the BackendConfig CRD. My current BackendConfig looks like this:

apiVersion: cloud.google.com/v1
kind: BackendConfig
metadata:
  name: XXX-hc-config
spec:
  healthCheck:
    checkIntervalSec: 15
    timeoutSec: 5
    port: 8080
    type: HTTP
    requestPath: /healthz

As seen in the link above, Google DOES support content-based health checks. But I cannot see, how to configure this. I expected something like:

healthCheck:
    checkIntervalSec: 15
    timeoutSec: 5
    port: 8080
    type: HTTP
    requestPath: /healthz
    response: "OK" <--- THIS IS NEW

but I cannot find anything about it. Not even in the CRD source code. Did anyone ever do this successfully? How?

In the GCP console you can set it like this:

Screenshot 2024-02-15 at 14 40 38

@raweber42
Copy link
Author

Is there another place where I can address this issues? It's rather urgent.

@swetharepakula
Copy link
Member

/kind feature

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 6, 2024
@raweber42
Copy link
Author

I would be willing to contribute on this one :)

@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 9, 2024
@raweber42
Copy link
Author

I said, I am willing to contribute @k8s-ci-robot 🤣

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active 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 rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants