blog: rephrase the article update
this blog post was modified as part of #29740 but IMO the update note doesn't make it clear enough what's going on.pull/30935/head
parent
7012c979f5
commit
a5da40b917
|
@ -4,10 +4,12 @@ title: 'Health checking gRPC servers on Kubernetes'
|
|||
date: 2018-10-01
|
||||
---
|
||||
|
||||
_Built-in gRPC probes were introduced in Kubernetes 1.23. To learn more, see [Configure Liveness, Readiness and Startup Probes](/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-a-grpc-liveness-probe)._
|
||||
|
||||
**Author**: [Ahmet Alp Balkan](https://twitter.com/ahmetb) (Google)
|
||||
|
||||
**Update (December 2021):** _Kubernetes now has built-in gRPC health probes starting in v1.23.
|
||||
To learn more, see [Configure Liveness, Readiness and Startup Probes](/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-a-grpc-liveness-probe).
|
||||
This article was originally written about an external tool to achieve the same task._
|
||||
|
||||
[gRPC](https://grpc.io) is on its way to becoming the lingua franca for
|
||||
communication between cloud-native microservices. If you are deploying gRPC
|
||||
applications to Kubernetes today, you may be wondering about the best way to
|
||||
|
|
Loading…
Reference in New Issue