2 top-level fields · unchanged since Istio 1.22.0
`WorkloadGroup` enables specifying the properties of a single workload for bootstrap and provides a template for `WorkloadEntry`, similar to how `Deployment` specifies properties of workloads via `Pod` templates.
Metadata that will be used for all corresponding `WorkloadEntries`.
`ReadinessProbe` describes the configuration the user must provide for healthchecking on their workload.
Health is determined by how the command that is executed exited.
Command to run.
Minimum consecutive failures for the probe to be considered failed after having succeeded.
`httpGet` is performed to a given endpoint and the status/able to connect determines health.
Host name to connect to, defaults to the pod IP.
Headers the proxy will pass on to make the request.
Path to access on the HTTP server.
Port on which the endpoint lives.
Number of seconds after the container has started before readiness probes are initiated.
How often (in seconds) to perform the probe.
Minimum consecutive successes for the probe to be considered successful after having failed.
Health is determined by if the proxy is able to connect.
Number of seconds after which the probe times out.
Template to be used for the generation of `WorkloadEntry` resources that belong to this `WorkloadGroup`.
Address associated with the network endpoint without the port.
One or more labels associated with the endpoint.
The locality associated with the endpoint.
Network enables Istio to group endpoints resident in the same L3 domain/network.
Set of ports associated with the endpoint.
The service account associated with the workload if a sidecar is present in the workload.
The load balancing weight associated with the endpoint.
Source: crd-all.gen.yaml
Changes to WorkloadGroup (networking.istio.io/v1) in each Istio version, compared to the version before it.
WorkloadGroup was first seen on this version of Istio
Released · View WorkloadGroup in 1.22.0
No examples of WorkloadGroup yet. Contribute one on GitHub.
kubespec.dev