-
Notifications
You must be signed in to change notification settings - Fork 160
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
chore(chart): start using Kubernetes' builtin gRPC probe #3041
Conversation
Signed-off-by: Hidde Beydals <[email protected]>
✅ Deploy Preview for docs-kargo-io ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
This kind of conflicts with what is being attempted in #2906. |
Let's get this in ahead of #2906. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3041 +/- ##
=======================================
Coverage 51.10% 51.10%
=======================================
Files 283 283
Lines 25398 25398
=======================================
Hits 12979 12979
Misses 11720 11720
Partials 699 699 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Hidde Beydals <[email protected]> Signed-off-by: Diego Caspi <[email protected]>
Signed-off-by: Hidde Beydals <[email protected]>
Related to #3038
This starts to make use of the builtin gRPC probe in an attempt to eventually drop our dependency on
grpc_health_probe
.Sadly, however, the builtin probe does not support TLS (kubernetes/kubernetes#128365) (or disabling verification), and we can thus not drop the
grpc_health_probe
binary yet.