temporalio / temporalio/temporal
Expose anonymous HTTP/HTTPS health endpoint on Frontend
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
When the frontend which is installed on kubernetes is exposed to Internet via ingress load balancer, the load balancer requires a health endpoint for the health-checks. When the client authentication is enabled by mTLS the health check fails and the load balancer marks the frontend pods as failed. Therefore the setup is not functional.
Most cloud load balancers today don"t support the client certificate auth. For example we use GKE.
Describe the solution you'd like
Enable a health endpoint without auth so the load balancer can use it for health checks,
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Temporal frontend's HTTP/HTTPS entry point and review how mTLS or client authentication is applied. Verify that a health endpoint works anonymously through a Kubernetes ingress or load-balancer health check while authentication remains required elsewhere; the issue names no file or test, so locate those first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100