Healthcheck keeps failing
- Dominant language
- Go
- Stars
- 11.7k
- Forks
- 802
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 80
Description
I keep getting `Readiness probe failed: Get "http://10.2.9.133:4040/ready": dial tcp 10.2.9.133:4040: connect: connection refused` error in gke cluster. Following is the healthcheck settings I have:
```
readinessProbe:
httpGet:
path: /ready
port: 4040
livenessProbe:
httpGet:
path: /ready
port: 4040
initialDelaySeconds: 180
timeoutSeconds: 30
failureThreshold: 10
```
Am I using incorrect path? can someone please guide? many thanks in advance.
Contributor guide
No contributing guide indexed for this repository
Research direction
The report mentions GKE readiness and liveness probes targeting /ready on port 4040, but names no repository file or test. Start by locating the deployment configuration and checking which endpoint and port the application exposes; done means the probes reach a valid healthcheck endpoint without connection-refused failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100