diff --git a/content/en/docs/reference/config/istio.mesh.v1alpha1/index.html b/content/en/docs/reference/config/istio.mesh.v1alpha1/index.html index 5c7d38019b..4ffa0978b2 100644 --- a/content/en/docs/reference/config/istio.mesh.v1alpha1/index.html +++ b/content/en/docs/reference/config/istio.mesh.v1alpha1/index.html @@ -432,6 +432,19 @@ No All control planes running in the same service mesh should specify the same mesh ID. Mesh ID is used to label telemetry reports for cases where telemetry from multiple meshes is mixed together.
+ +readinessProbe
ReadinessProbe
VM Health Checking readiness probe. This health check config exactly mirrors the +kubernetes readiness probe configuration both in schema and logic. +Only one health check method of 3 can be set at a time.
+WorkloadGroup
describes a collection of workload instances.
It provides a specification that the workload instances can use to bootstrap
@@ -42,6 +42,20 @@ spec:
grpc: 3550
http: 8080
serviceAccount: default
+ probe:
+ initialDelaySeconds: 5
+ timeoutSeconds: 3
+ periodSeconds: 4
+ successThreshold: 3
+ failureThreshold: 3
+ httpGet:
+ path: /foo/bar
+ host: 127.0.0.1
+ port: 3100
+ scheme: https
+ httpHeaders:
+ - name: Lit-Header
+ value: Im-The-Best
{{}}
@@ -92,6 +106,298 @@ workload group, and inherit the labels and annotations from the above meta
Yes
probe
ReadinessProbe
ReadinessProbe
describes the configuration the user must provide for healthchecking on their workload.
+This configuration mirrors K8S in both syntax and logic for the most part.