Get desktop application:
View/edit binary Protocol Buffers messages
AndConstraint represents a logical 'and' of constraints.
Used in:
CommandSpec describes a command to be run in the container.
Used in:
,value is the command line to execute inside the container.
Arguments to the command.
Constraint represents a host label constraint or a related pods label constraint. This is used to require that a host have certain label constraints or to require that the pods already running on the host have certain label constraints.
Used in:
, , ,Used in:
Reserved for compatibility.
A single application container running inside a pod.
Used in:
Name of the container. Each container in a pod must have a unique name. Cannot be updated.
Resource config of the container
Container config of the container Deprecated.
Command line config of the container Deprecated.
Custom executor config of the task. Deprecated.
Liveness health check config of the container
Readiness health check config of the container This is currently not supported.
List of network ports to be allocated for the container. These ports will be assigned on the pod network namespace if the pod has its own network name space. If the pod does not have its own network name space, the ports will be assigned on the host network.
Entrypoint command.
List of environment variables to set in the container.
Image name.
Pod volumes to mount into the container's filesystem.
Runtime states of a container in a pod.
Used in:
Invalid state.
The container has not been created yet.
The container has been launched.
The container is being started on a host.
The container is running on a host.
The container terminated with an exit code of zero.
The container terminated with a non-zero exit code.
The container is being killed.
Execution of the container was terminated by the system.
Runtime status of a container in a pod.
Used in:
,Name of the container
Runtime state of the container.
Dynamic ports reserved on the host while this container is running.
The message that explains the current state of a container such as why the container is failed. Only track the latest one if the container has been retried and failed multiple times.
The reason that explains the current state of a container. Only track the latest one if the container has been retried and failed multiple times.
The number of times the container has failed after retries.
The result of the health check.
The image the container is running.
The time when the container starts to run. Will be unset if the pod hasn't started running yet. The time is represented in RFC3339 form with UTC timezone.
The time when the container terminated. Will be unset if the pod hasn't completed yet. The time is represented in RFC3339 form with UTC timezone.
Termination status of the task. Set only if the task is in a non-successful terminal state such as CONTAINER_STATE_FAILED or CONTAINER_STATE_KILLED.
Environment represents an environment variable present in a container.
Used in:
Name of the environment variable.
Value of the environment variable.
HTTPGetSpec describes an action based on HTTP Get request.
Used in:
The scheme to use for connecting to the host. Currently http and https are supported.
Port to send the HTTP GET. Deprecated.
The request path on the HTTP server.
Custom HTTP headers to set in the request. HTTP allows repeated headers.
Port to send the HTTP GET.
HTTPHeader describes a custom HTTP header to be used in the HTTP request.
Used in:
The header field name
The header field value
Health check configuration for a container.
Used in:
Whether the health check is enabled.
Start time wait in seconds. Default value is 15.
Interval in seconds between two health checks. Default value is 10.
Max number of consecutive failures before failing health check. Default value is 3.
Health check command timeout in seconds. Default value is 20.
Type of health check to run.
Only applicable when type is `COMMAND`. Deprecated
Only applicable when type is 'HTTP'. Deprecated
Minimum consecutive successes for the health check to be considered successful after a failure. Defaults to 1. Only available in the Kubelet runtime.
Command to run in the container to do the health check. Only applicable when type is `COMMAND`.
HTTP Get request to perform. Only applicable when type is 'HTTP'.
Deprecated.
Used in:
Health check command to be executed. Note that this command by default inherits all environment varibles from the container it's monitoring, unless `unshare_environments` is set to true.
If set, this check will not share the environment variables of the container.
Deprecated.
HTTP health check to be executed. Sends a GET request to scheme://<host>:port/path. Host is not configurable and is resolved automatically.
Used in:
Currently http and https are supported.
Port to send the HTTP GET.
The request path.
Type of health check to run.
Used in:
Reserved for future compatibility of new types.
Command line based health check
HTTP endpoint based health check
HealthState is the health check state of a container.
Used in:
Default value.
If the health check config is not enabled in the container config, then the health state is DISABLED.
If the health check config is enabled in the container config, but the container has not reported the output of the health check yet, then the health state is UNKNOWN.
The container passes the health check.
The container failed to pass the health check.
The result of the health check.
Used in:
The health check state.
The output of the health check run.
Pod InstanceID range [from, to)
Used in:
, , ,LabelConstraint represents a constraint on the number of occurrences of a given label from the set of host labels or pod labels present on the host.
Used in:
Determines which labels the constraint should apply to.
Determines which constraint there should be on the number of occurrences of the label.
The label which this defines a constraint on: For Kind == HOST, each attribute on host agent is transformed to a label, with `hostname` as a special label which is always inferred from agent hostname and set.
A limit on the number of occurrences of the label.
Condition represents a constraint on the number of occurrences of the label.
Used in:
Kind represents whatever the constraint applies to the labels on the host or to the labels of the pods that are located on the host.
Used in:
OrConstraint represents a logical 'or' of constraints.
Used in:
Persistent volume configuration for a pod. Deprecated
Used in:
Volume mount path inside container.
Volume size in MB.
Pod events of a particular run of a job instance.
Used in:
,The current pod ID.
Actual state of a pod.
Goal State of a pod.
The time when the event was created. The time is represented in RFC3339 form with UTC timezone.
The entity version currently used by the pod.
The desired entity version that should be used by the pod.
The agentID for the pod.
The host on which the pod is running.
Short human friendly message explaining state.
The short reason for the pod event.
The previous pod ID.
The health check result of the pod.
The desired pod ID.
Status of the containers.
Status of the init containers.
Info of a pod in a Job.
Used in:
,Configuration of the pod.
Runtime status of the pod.
Pod configuration for a given job instance Note that only add string/slice/ptr type into PodConfig directly due to the limitation of go reflection inside our pod specific config logic.
Used in:
, ,Name of the pod
List of user-defined labels for the pod
List of initialization containers belonging to the pod. These containers are assumed to run to completion and are executed in order prior to containers being started. If any init container fails, the pod is considered to have failed. Init containers cannot be configured to have readiness or liveness health checks.
List of containers belonging to the pod. These will be started in parallel after init containers terminate. There must be at least one container in a pod.
Constraint on the attributes of the host or labels on pods on the host that this pod should run on. Use `AndConstraint`/`OrConstraint` to compose multiple constraints if necessary.
Pod restart policy on failures
Persistent volume config of the pod. Deprecated
Preemption policy of the pod
Whether this is a controller pod. A controller is a special batch pod which controls other pods inside a job. E.g. spark driver pods in a spark job will be a controller pod.
This is used to set the amount of time between when the executor sends the SIGTERM message to gracefully terminate a pod and when it kills it by sending SIGKILL. If you do not set the grace period duration the default is 30 seconds.
revocable represents pod to use physical or slack resources.
List of volumes that can be mounted by containers belonging to the pod.
Extra configuration specific to the Mesos runtime. Experimental and is subject to change.
List of network ports to be allocated for all the containers in the pod on the host network.
Runtime states of a pod instance.
Used in:
,Invalid state.
The pod is being initialized.
The pod is pending and waiting for resources.
The pod has been allocated with resources and ready for placement.
The pod is being placed to a host based on its resource requirements and constraints.
The pod has been assigned to a host matching the resource requirements and constraints.
The pod is taken from resmgr to be launched.
The pod is being launched in Job manager.
Either init containers are starting/running or the main containers in the pod are being started.
All containers in the pod are running.
All containers in the pod terminated with an exit code of zero.
At least on container in the pod terminated with a non-zero exit code.
The pod is lost.
The pod is being killed.
At least one of the containers in the pod was terminated by the system.
The pod is being preempted by another one on the node.
The pod is to be deleted after termination.
The pod is to be reserved on a node.
Runtime status of a pod instance in a Job.
Used in:
, ,Runtime state of the pod.
The current pod ID for this pod.
The time when the pod starts to run. Will be unset if the pod hasn't started running yet. The time is represented in RFC3339 form with UTC timezone.
The time when the pod is completed. Will be unset if the pod hasn't completed yet. The time is represented in RFC3339 form with UTC timezone.
The name of the host where the pod is running.
Status of the init containers.
Status of the containers.
The desired state of the pod which should be eventually reached by the system.
The message that explains the current state of a pod.
The reason that explains the current state of a pod.
The number of times the pod has failed after retries.
persistent volume id. Deprecated.
The entity version currently used by the pod. TODO Avoid leaking job abstractions into public pod APIs. Remove after internal protobuf structures are defined.
The desired entity version that should be used by the pod. TODO Avoid leaking job abstractions into public pod APIs. Remove after internal protobuf structures are defined.
the id of mesos agent on the host to be launched. Deprecated.
Revision of the current pod status.
The pod id of the previous pod.
The resource usage for this pod. The map key is each resource kind in string format and the map value is the number of unit-seconds of that resource used by the job. Example: if a pod that uses 1 CPU and finishes in 10 seconds, this map will contain <"cpu":10>.
The desired pod ID for this pod.
The name of the host where the pod should be running on upon restart. It is used for best effort in-place update/restart.
The identifier for the host runtime agent.
Summary information about a pod.
Used in:
,Name of the pod.
Runtime status of the pod.
Network port configuration for a container.
Used in:
, ,Name of the network port, e.g. http, tchannel. Required field.
Static port number assigned. Only applicable when type is PORT_TYPE_STATIC.
Environment variable name to be exported when running a container for this port. Only applicable when type is PORT_TYPE_DYNAMIC_ENV_VAR.
Template variable for a dynamic port in the format: {{port.$NAME}}, where $NAME is a unique name of the port that can contain characters 'a'-'z', '-', '_' and '.'. This variable can be used in other parts of PodSpec to reference a port value (for example in env variables). Specifying a port as a template variable allows communicating the value of the port between containers in the pod. Only applicable when type is PORT_TYPE_DYNAMIC_TEMPLATE_VAR.
Type of the port
Type of the port
Used in:
Invalid port type
Static port
Dynamic port that will be exported into environment variable
Dynamic port specified as a template variable
Preemption policy for a pod.
Used in:
This policy defines if the pod should be restarted after it is preempted. If set to true the pod will not be rescheduled after it is preempted. If set to false the pod will be rescheduled. Defaults to false
QuerySpec specifies the list of query criteria for pods. All indexed fields should be part of this message. And all fields in this message have to be indexed too.
Used in:
The spec of how to do pagination for the query results.
List of pod states to query the pods. Will match all pods if the list is empty.
List of pod names to query the pods. Will match all names if the list is empty.
List of hosts to query the pods. Will match all hosts if the list is empty.
Resource configuration for a container.
Used in:
,CPU limit in number of CPU cores.
Memory limit in MB.
Disk limit in MB.
File descriptor limit.
GPU limit in number of GPUs.
Restart policy for a pod.
Used in:
Max number of pod failures can occur before giving up scheduling retry, no backoff for now. Default 0 means no retry on failures.
TerminationStatus contains details about termination of a task. It mainly contains Peloton-specific reasons for termination.
Used in:
Reason for termination.
If non-zero, exit status when the container terminated.
Name of signal received by the container when it terminated.
Reason lists various causes for a task termination
Used in:
Default value.
Task was killed because a stop request was received from a client.
Task failed. See also TerminationStatus.exit_code, TerminationStatus.signal and ContainerStatus.message.
Task was killed to put the host in to maintenance.
Task was killed to reclaim resources allocated to it.
Task was killed due to deadline tracker exceeding task timeout
Task was killed for update
Task was killed for restart
Task was killed for sla aware restart
VolumeMount describes a mounting of a Volume within a container.
Used in:
This must match the Name of a Volume in the PodSpec.
Mounted read-only if true, read-write otherwise (false or unspecified).
Path within the container at which the volume should be mounted.