hashicorp / hashicorp/vault-helm
http: TLS handshake error from 10.128.0.110:59890: no certificate available
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 898
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 1
Description
pod hashicorp-vault-agent-injector- in CrashLoopBackOff
```
2021-04-20T17:07:08.646Z [INFO] handler: Starting handler..
Listening on ":8080"...
2021-04-20T17:07:08.658Z [INFO] handler.auto-tls: Generated CA
2021-04-20T17:07:08.659Z [INFO] handler.certwatcher: Updated certificate bundle received. Updating certs...
2021/04/20 17:07:14 http: TLS handshake error from 10.128.0.110:59880: no certificate available
2021/04/20 17:07:14 http: TLS handshake error from 10.128.0.110:59882: no certificate available
2021/04/20 17:07:16 http: TLS handshake error from 10.128.0.110:59888: no certificate available
2021/04/20 17:07:16 http: TLS handshake error from 10.128.0.110:59890: no certificate available
```
Contributor guide
Research direction
No file or test is named. Start by inspecting the Helm chart configuration for the vault-agent-injector pod and its auto-TLS certificate setup, then correlate that configuration with the recorded TLS handshake errors and CrashLoopBackOff state. Done means identifying the cause and documenting or implementing a verified fix for certificate availability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100