-
Notifications
You must be signed in to change notification settings - Fork 9
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
gRPC probes instead of Exec probes #391
Labels
area/configuration
concept/attractor
concept/conduit
concept/trench
kind/enhancement
New feature or request
Comments
LionelJouin
added
kind/enhancement
New feature or request
concept/trench
concept/conduit
concept/attractor
area/configuration
labels
Mar 6, 2023
Benchmark to see if there is any improvement:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/configuration
concept/attractor
concept/conduit
concept/trench
kind/enhancement
New feature or request
Is your feature request related to a problem? Please describe.
Due to the ExecProbes, the userspaces program might be slower than expected. NFQLB in the stateless-lb might have some latency and performance issues.
We use Exec probes because the probes are exposed via GRPC, so we use this project for health checking: https://github.com/grpc-ecosystem/grpc-health-probe
Describe the solution you'd like
Since Kubernetes 1.23, GRPC probes is a native feature, it can be enabled via the
GRPCContainerProbe
feature gate, and is already enabled from Kubernetes 1.24.We must replace all Exec probes by GRPC probes in all components for Kubernetes 1.24 deployment.
Describe alternatives you've considered
/
Additional context
/
The text was updated successfully, but these errors were encountered: