Workload Group

    The following example declares a workload group representing a collection of workloads that will be registered under reviews in namespace bookinfo. The set of labels will be associated with each workload instance during the bootstrap process, and the ports 3550 and 8080 will be associated with the workload group and use service account default. app.kubernetes.io/version is just an arbitrary example of a label.

    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. A WorkloadGroup can have more than one WorkloadEntry. WorkloadGroup has no relationship to resources which control service registry like ServiceEntry and as such doesn’t configure host name for these workloads.

    ReadinessProbe

    FieldTypeDescriptionRequired
    initialDelaySecondsint32

    Number of seconds after the container has started before readiness probes are initiated.

    No
    timeoutSecondsint32

    Number of seconds after which the probe times out. Defaults to 1 second. Minimum value is 1 second.

    No
    periodSecondsint32

    How often (in seconds) to perform the probe. Default to 10 seconds. Minimum value is 1 second.

    No
    successThresholdint32No
    failureThresholdint32

    Minimum consecutive failures for the probe to be considered failed after having succeeded. Defaults to 3 seconds.

    No
    httpGet

    httpGet is performed to a given endpoint and the status/able to connect determines health.

    No
    tcpSocketTCPHealthCheckConfig (oneof)

    Health is determined by if the proxy is able to connect.

    No
    exec

    Health is determined by how the command that is executed exited.

    No

    HTTPHeader

    FieldTypeDescriptionRequired
    namestring

    The header field name

    No
    valuestring

    The header field value

    No

    ExecHealthCheckConfig

    FieldTypeDescriptionRequired
    commandstring[]

    Command to run. Exit status of 0 is treated as live/healthy and non-zero is unhealthy.

    No

    ObjectMeta describes metadata that will be attached to a WorkloadEntry. It is a subset of the supported Kubernetes metadata.