spring-projects / spring-projects/spring-grpc
Allow to have the health probes without TLS
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 413
- Forks
- 95
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 2
Description
Hello.
In K8s / OCP deployment environments, the gRPC probes don't support TLS.
Unfortunately, the server SSL configuration gets applied globally (for what I can see/read) and therefore it then protects also the Health service.
Would it be possible to have some sort of configuration where to say that some services should not be protected through TLS?
Or, alternatively, is there maybe a way to do this already?
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 by tracing how the server SSL configuration is applied to the gRPC Health service and how Kubernetes/OCP gRPC probes connect. Determine whether existing configuration can exempt selected services from TLS or whether a new configuration capability is needed; done means health probes work without TLS while other services remain protected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, java, kubernetes
- Domain
- api, devops, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100