- 3.61.0 (latest)
- 3.60.0
- 3.59.0
- 3.58.0
- 3.57.0
- 3.56.0
- 3.55.0
- 3.54.0
- 3.53.0
- 3.52.0
- 3.50.0
- 3.49.0
- 3.48.0
- 3.47.0
- 3.46.0
- 3.45.0
- 3.44.0
- 3.43.0
- 3.42.0
- 3.41.0
- 3.40.0
- 3.38.0
- 3.37.0
- 3.36.0
- 3.35.0
- 3.34.0
- 3.33.0
- 3.32.0
- 3.31.0
- 3.30.0
- 3.29.0
- 3.28.0
- 3.25.0
- 3.24.0
- 3.23.0
- 3.22.0
- 3.21.0
- 3.20.0
- 3.19.0
- 3.18.0
- 3.17.0
- 3.16.0
- 3.15.0
- 3.14.0
- 3.13.0
- 3.12.0
- 3.11.0
- 3.10.0
- 3.9.0
- 3.8.0
- 3.7.0
- 3.6.0
- 3.5.0
- 3.4.2
- 3.3.0
- 3.2.0
- 3.0.0
- 2.9.8
- 2.8.9
- 2.7.4
- 2.5.3
- 2.4.0
public static final class ModelContainerSpec.Builder extends GeneratedMessageV3.Builder<ModelContainerSpec.Builder> implements ModelContainerSpecOrBuilderSpecification of a container for serving predictions. Some fields in this message correspond to fields in the Kubernetes Container v1 core specification.
Protobuf type google.cloud.aiplatform.v1beta1.ModelContainerSpec
Inheritance
Object > AbstractMessageLite.Builder<MessageType,BuilderType> > AbstractMessage.Builder<BuilderType> > GeneratedMessageV3.Builder > ModelContainerSpec.BuilderImplements
ModelContainerSpecOrBuilderStatic Methods
getDescriptor()
public static final Descriptors.Descriptor getDescriptor()| Returns | |
|---|---|
| Type | Description |
Descriptor | |
Methods
addAllArgs(Iterable<String> values)
public ModelContainerSpec.Builder addAllArgs(Iterable<String> values) Immutable. Specifies arguments for the command that runs when the container
starts. This overrides the container's
CMD. Specify
this field as an array of executable and arguments, similar to a Docker
CMD's "default parameters" form.
If you don't specify this field but do specify the
command
field, then the command from the command field runs without any
additional arguments. See the Kubernetes documentation about how the
command and args fields interact with a container's ENTRYPOINT and
CMD.
If you don't specify this field and don't specify the command field,
then the container's
ENTRYPOINT and
CMD determine what runs based on their default behavior. See the Docker
documentation about how CMD and ENTRYPOINT
interact.
In this field, you can reference environment variables
set by Vertex
AI
and environment variables set in the
env field. You
cannot reference environment variables set in the Docker image. In order
for environment variables to be expanded, reference them by using the
following syntax:
<code>$(<var>VARIABLE_NAME</var>)</code>
Note that this differs from Bash variable expansion, which does not use
parentheses. If a variable cannot be resolved, the reference in the input
string is used unchanged. To avoid variable expansion, you can escape this
syntax with $$; for example:
<code>$$(<var>VARIABLE_NAME</var>)</code>
This field corresponds to the args field of the Kubernetes Containers
v1 core
API.
repeated string args = 3 [(.google.api.field_behavior) = IMMUTABLE];
| Parameter | |
|---|---|
| Name | Description |
values | Iterable<String>The args to add. |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | This builder for chaining. |
addAllCommand(Iterable<String> values)
public ModelContainerSpec.Builder addAllCommand(Iterable<String> values) Immutable. Specifies the command that runs when the container starts. This
overrides the container's
ENTRYPOINT.
Specify this field as an array of executable and arguments, similar to a
Docker ENTRYPOINT's "exec" form, not its "shell" form.
If you do not specify this field, then the container's ENTRYPOINT runs,
in conjunction with the
args field or
the container's
CMD, if either
exists. If this field is not specified and the container does not have an
ENTRYPOINT, then refer to the Docker documentation about how CMD and
ENTRYPOINT
interact.
If you specify this field, then you can also specify the args field to
provide additional arguments for this command. However, if you specify this
field, then the container's CMD is ignored. See the
Kubernetes documentation about how the
command and args fields interact with a container's ENTRYPOINT and
CMD.
In this field, you can reference environment variables set by Vertex
AI
and environment variables set in the
env field. You
cannot reference environment variables set in the Docker image. In order
for environment variables to be expanded, reference them by using the
following syntax:
<code>$(<var>VARIABLE_NAME</var>)</code>
Note that this differs from Bash variable expansion, which does not use
parentheses. If a variable cannot be resolved, the reference in the input
string is used unchanged. To avoid variable expansion, you can escape this
syntax with $$; for example:
<code>$$(<var>VARIABLE_NAME</var>)</code>
This field corresponds to the command field of the Kubernetes Containers
v1 core
API.
repeated string command = 2 [(.google.api.field_behavior) = IMMUTABLE];
| Parameter | |
|---|---|
| Name | Description |
values | Iterable<String>The command to add. |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | This builder for chaining. |
addAllEnv(Iterable<? extends EnvVar> values)
public ModelContainerSpec.Builder addAllEnv(Iterable<? extends EnvVar> values)Immutable. List of environment variables to set in the container. After the container starts running, code running in the container can read these environment variables.
Additionally, the
command and
args fields can
reference these variables. Later entries in this list can also reference
earlier entries. For example, the following example sets the variable
VAR_2 to have the value foo bar:
`json
[
{
"name": "VAR_1",
"value": "foo"
},
{
"name": "VAR_2",
"value": "$(VAR_1) bar"
}
]
If you switch the order of the variables in the example, then the expansion
does not occur.
This field corresponds to the env` field of the Kubernetes Containers
v1 core
API.
repeated .google.cloud.aiplatform.v1beta1.EnvVar env = 4 [(.google.api.field_behavior) = IMMUTABLE];
| Parameter | |
|---|---|
| Name | Description |
values | Iterable<? extends com.google.cloud.aiplatform.v1beta1.EnvVar> |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | |
addAllGrpcPorts(Iterable<? extends Port> values)
public ModelContainerSpec.Builder addAllGrpcPorts(Iterable<? extends Port> values)Immutable. List of ports to expose from the container. Vertex AI sends gRPC prediction requests that it receives to the first port on this list. Vertex AI also sends liveness and health checks to this port.
If you do not specify this field, gRPC requests to the container will be disabled.
Vertex AI does not use ports other than the first one listed. This field
corresponds to the ports field of the Kubernetes Containers v1 core API.
repeated .google.cloud.aiplatform.v1beta1.Port grpc_ports = 9 [(.google.api.field_behavior) = IMMUTABLE];
| Parameter | |
|---|---|
| Name | Description |
values | Iterable<? extends com.google.cloud.aiplatform.v1beta1.Port> |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | |
addAllPorts(Iterable<? extends Port> values)
public ModelContainerSpec.Builder addAllPorts(Iterable<? extends Port> values)Immutable. List of ports to expose from the container. Vertex AI sends any prediction requests that it receives to the first port on this list. Vertex AI also sends liveness and health checks to this port.
If you do not specify this field, it defaults to following value:
`json
[
{
"containerPort": 8080
}
]
Vertex AI does not use ports other than the first one listed. This field
corresponds to the ports` field of the Kubernetes Containers
v1 core
API.
repeated .google.cloud.aiplatform.v1beta1.Port ports = 5 [(.google.api.field_behavior) = IMMUTABLE];
| Parameter | |
|---|---|
| Name | Description |
values | Iterable<? extends com.google.cloud.aiplatform.v1beta1.Port> |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | |
addArgs(String value)
public ModelContainerSpec.Builder addArgs(String value) Immutable. Specifies arguments for the command that runs when the container
starts. This overrides the container's
CMD. Specify
this field as an array of executable and arguments, similar to a Docker
CMD's "default parameters" form.
If you don't specify this field but do specify the
command
field, then the command from the command field runs without any
additional arguments. See the Kubernetes documentation about how the
command and args fields interact with a container's ENTRYPOINT and
CMD.
If you don't specify this field and don't specify the command field,
then the container's
ENTRYPOINT and
CMD determine what runs based on their default behavior. See the Docker
documentation about how CMD and ENTRYPOINT
interact.
In this field, you can reference environment variables
set by Vertex
AI
and environment variables set in the
env field. You
cannot reference environment variables set in the Docker image. In order
for environment variables to be expanded, reference them by using the
following syntax:
<code>$(<var>VARIABLE_NAME</var>)</code>
Note that this differs from Bash variable expansion, which does not use
parentheses. If a variable cannot be resolved, the reference in the input
string is used unchanged. To avoid variable expansion, you can escape this
syntax with $$; for example:
<code>$$(<var>VARIABLE_NAME</var>)</code>
This field corresponds to the args field of the Kubernetes Containers
v1 core
API.
repeated string args = 3 [(.google.api.field_behavior) = IMMUTABLE];
| Parameter | |
|---|---|
| Name | Description |
value | StringThe args to add. |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | This builder for chaining. |
addArgsBytes(ByteString value)
public ModelContainerSpec.Builder addArgsBytes(ByteString value) Immutable. Specifies arguments for the command that runs when the container
starts. This overrides the container's
CMD. Specify
this field as an array of executable and arguments, similar to a Docker
CMD's "default parameters" form.
If you don't specify this field but do specify the
command
field, then the command from the command field runs without any
additional arguments. See the Kubernetes documentation about how the
command and args fields interact with a container's ENTRYPOINT and
CMD.
If you don't specify this field and don't specify the command field,
then the container's
ENTRYPOINT and
CMD determine what runs based on their default behavior. See the Docker
documentation about how CMD and ENTRYPOINT
interact.
In this field, you can reference environment variables
set by Vertex
AI
and environment variables set in the
env field. You
cannot reference environment variables set in the Docker image. In order
for environment variables to be expanded, reference them by using the
following syntax:
<code>$(<var>VARIABLE_NAME</var>)</code>
Note that this differs from Bash variable expansion, which does not use
parentheses. If a variable cannot be resolved, the reference in the input
string is used unchanged. To avoid variable expansion, you can escape this
syntax with $$; for example:
<code>$$(<var>VARIABLE_NAME</var>)</code>
This field corresponds to the args field of the Kubernetes Containers
v1 core
API.
repeated string args = 3 [(.google.api.field_behavior) = IMMUTABLE];
| Parameter | |
|---|---|
| Name | Description |
value | ByteStringThe bytes of the args to add. |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | This builder for chaining. |
addCommand(String value)
public ModelContainerSpec.Builder addCommand(String value) Immutable. Specifies the command that runs when the container starts. This
overrides the container's
ENTRYPOINT.
Specify this field as an array of executable and arguments, similar to a
Docker ENTRYPOINT's "exec" form, not its "shell" form.
If you do not specify this field, then the container's ENTRYPOINT runs,
in conjunction with the
args field or
the container's
CMD, if either
exists. If this field is not specified and the container does not have an
ENTRYPOINT, then refer to the Docker documentation about how CMD and
ENTRYPOINT
interact.
If you specify this field, then you can also specify the args field to
provide additional arguments for this command. However, if you specify this
field, then the container's CMD is ignored. See the
Kubernetes documentation about how the
command and args fields interact with a container's ENTRYPOINT and
CMD.
In this field, you can reference environment variables set by Vertex
AI
and environment variables set in the
env field. You
cannot reference environment variables set in the Docker image. In order
for environment variables to be expanded, reference them by using the
following syntax:
<code>$(<var>VARIABLE_NAME</var>)</code>
Note that this differs from Bash variable expansion, which does not use
parentheses. If a variable cannot be resolved, the reference in the input
string is used unchanged. To avoid variable expansion, you can escape this
syntax with $$; for example:
<code>$$(<var>VARIABLE_NAME</var>)</code>
This field corresponds to the command field of the Kubernetes Containers
v1 core
API.
repeated string command = 2 [(.google.api.field_behavior) = IMMUTABLE];
| Parameter | |
|---|---|
| Name | Description |
value | StringThe command to add. |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | This builder for chaining. |
addCommandBytes(ByteString value)
public ModelContainerSpec.Builder addCommandBytes(ByteString value) Immutable. Specifies the command that runs when the container starts. This
overrides the container's
ENTRYPOINT.
Specify this field as an array of executable and arguments, similar to a
Docker ENTRYPOINT's "exec" form, not its "shell" form.
If you do not specify this field, then the container's ENTRYPOINT runs,
in conjunction with the
args field or
the container's
CMD, if either
exists. If this field is not specified and the container does not have an
ENTRYPOINT, then refer to the Docker documentation about how CMD and
ENTRYPOINT
interact.
If you specify this field, then you can also specify the args field to
provide additional arguments for this command. However, if you specify this
field, then the container's CMD is ignored. See the
Kubernetes documentation about how the
command and args fields interact with a container's ENTRYPOINT and
CMD.
In this field, you can reference environment variables set by Vertex
AI
and environment variables set in the
env field. You
cannot reference environment variables set in the Docker image. In order
for environment variables to be expanded, reference them by using the
following syntax:
<code>$(<var>VARIABLE_NAME</var>)</code>
Note that this differs from Bash variable expansion, which does not use
parentheses. If a variable cannot be resolved, the reference in the input
string is used unchanged. To avoid variable expansion, you can escape this
syntax with $$; for example:
<code>$$(<var>VARIABLE_NAME</var>)</code>
This field corresponds to the command field of the Kubernetes Containers
v1 core
API.
repeated string command = 2 [(.google.api.field_behavior) = IMMUTABLE];
| Parameter | |
|---|---|
| Name | Description |
value | ByteStringThe bytes of the command to add. |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | This builder for chaining. |
addEnv(EnvVar value)
public ModelContainerSpec.Builder addEnv(EnvVar value)Immutable. List of environment variables to set in the container. After the container starts running, code running in the container can read these environment variables.
Additionally, the
command and
args fields can
reference these variables. Later entries in this list can also reference
earlier entries. For example, the following example sets the variable
VAR_2 to have the value foo bar:
`json
[
{
"name": "VAR_1",
"value": "foo"
},
{
"name": "VAR_2",
"value": "$(VAR_1) bar"
}
]
If you switch the order of the variables in the example, then the expansion
does not occur.
This field corresponds to the env` field of the Kubernetes Containers
v1 core
API.
repeated .google.cloud.aiplatform.v1beta1.EnvVar env = 4 [(.google.api.field_behavior) = IMMUTABLE];
| Parameter | |
|---|---|
| Name | Description |
value | EnvVar |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | |
addEnv(EnvVar.Builder builderForValue)
public ModelContainerSpec.Builder addEnv(EnvVar.Builder builderForValue)Immutable. List of environment variables to set in the container. After the container starts running, code running in the container can read these environment variables.
Additionally, the
command and
args fields can
reference these variables. Later entries in this list can also reference
earlier entries. For example, the following example sets the variable
VAR_2 to have the value foo bar:
`json
[
{
"name": "VAR_1",
"value": "foo"
},
{
"name": "VAR_2",
"value": "$(VAR_1) bar"
}
]
If you switch the order of the variables in the example, then the expansion
does not occur.
This field corresponds to the env` field of the Kubernetes Containers
v1 core
API.
repeated .google.cloud.aiplatform.v1beta1.EnvVar env = 4 [(.google.api.field_behavior) = IMMUTABLE];
| Parameter | |
|---|---|
| Name | Description |
builderForValue | EnvVar.Builder |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | |
addEnv(int index, EnvVar value)
public ModelContainerSpec.Builder addEnv(int index, EnvVar value)Immutable. List of environment variables to set in the container. After the container starts running, code running in the container can read these environment variables.
Additionally, the
command and
args fields can
reference these variables. Later entries in this list can also reference
earlier entries. For example, the following example sets the variable
VAR_2 to have the value foo bar:
`json
[
{
"name": "VAR_1",
"value": "foo"
},
{
"name": "VAR_2",
"value": "$(VAR_1) bar"
}
]
If you switch the order of the variables in the example, then the expansion
does not occur.
This field corresponds to the env` field of the Kubernetes Containers
v1 core
API.
repeated .google.cloud.aiplatform.v1beta1.EnvVar env = 4 [(.google.api.field_behavior) = IMMUTABLE];
| Parameters | |
|---|---|
| Name | Description |
index | int |
value | EnvVar |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | |
addEnv(int index, EnvVar.Builder builderForValue)
public ModelContainerSpec.Builder addEnv(int index, EnvVar.Builder builderForValue)Immutable. List of environment variables to set in the container. After the container starts running, code running in the container can read these environment variables.
Additionally, the
command and
args fields can
reference these variables. Later entries in this list can also reference
earlier entries. For example, the following example sets the variable
VAR_2 to have the value foo bar:
`json
[
{
"name": "VAR_1",
"value": "foo"
},
{
"name": "VAR_2",
"value": "$(VAR_1) bar"
}
]
If you switch the order of the variables in the example, then the expansion
does not occur.
This field corresponds to the env` field of the Kubernetes Containers
v1 core
API.
repeated .google.cloud.aiplatform.v1beta1.EnvVar env = 4 [(.google.api.field_behavior) = IMMUTABLE];
| Parameters | |
|---|---|
| Name | Description |
index | int |
builderForValue | EnvVar.Builder |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | |
addEnvBuilder()
public EnvVar.Builder addEnvBuilder()Immutable. List of environment variables to set in the container. After the container starts running, code running in the container can read these environment variables.
Additionally, the
command and
args fields can
reference these variables. Later entries in this list can also reference
earlier entries. For example, the following example sets the variable
VAR_2 to have the value foo bar:
`json
[
{
"name": "VAR_1",
"value": "foo"
},
{
"name": "VAR_2",
"value": "$(VAR_1) bar"
}
]
If you switch the order of the variables in the example, then the expansion
does not occur.
This field corresponds to the env` field of the Kubernetes Containers
v1 core
API.
repeated .google.cloud.aiplatform.v1beta1.EnvVar env = 4 [(.google.api.field_behavior) = IMMUTABLE];
| Returns | |
|---|---|
| Type | Description |
EnvVar.Builder | |
addEnvBuilder(int index)
public EnvVar.Builder addEnvBuilder(int index)Immutable. List of environment variables to set in the container. After the container starts running, code running in the container can read these environment variables.
Additionally, the
command and
args fields can
reference these variables. Later entries in this list can also reference
earlier entries. For example, the following example sets the variable
VAR_2 to have the value foo bar:
`json
[
{
"name": "VAR_1",
"value": "foo"
},
{
"name": "VAR_2",
"value": "$(VAR_1) bar"
}
]
If you switch the order of the variables in the example, then the expansion
does not occur.
This field corresponds to the env` field of the Kubernetes Containers
v1 core
API.
repeated .google.cloud.aiplatform.v1beta1.EnvVar env = 4 [(.google.api.field_behavior) = IMMUTABLE];
| Parameter | |
|---|---|
| Name | Description |
index | int |
| Returns | |
|---|---|
| Type | Description |
EnvVar.Builder | |
addGrpcPorts(Port value)
public ModelContainerSpec.Builder addGrpcPorts(Port value)Immutable. List of ports to expose from the container. Vertex AI sends gRPC prediction requests that it receives to the first port on this list. Vertex AI also sends liveness and health checks to this port.
If you do not specify this field, gRPC requests to the container will be disabled.
Vertex AI does not use ports other than the first one listed. This field
corresponds to the ports field of the Kubernetes Containers v1 core API.
repeated .google.cloud.aiplatform.v1beta1.Port grpc_ports = 9 [(.google.api.field_behavior) = IMMUTABLE];
| Parameter | |
|---|---|
| Name | Description |
value | Port |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | |
addGrpcPorts(Port.Builder builderForValue)
public ModelContainerSpec.Builder addGrpcPorts(Port.Builder builderForValue)Immutable. List of ports to expose from the container. Vertex AI sends gRPC prediction requests that it receives to the first port on this list. Vertex AI also sends liveness and health checks to this port.
If you do not specify this field, gRPC requests to the container will be disabled.
Vertex AI does not use ports other than the first one listed. This field
corresponds to the ports field of the Kubernetes Containers v1 core API.
repeated .google.cloud.aiplatform.v1beta1.Port grpc_ports = 9 [(.google.api.field_behavior) = IMMUTABLE];
| Parameter | |
|---|---|
| Name | Description |
builderForValue | Port.Builder |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | |
addGrpcPorts(int index, Port value)
public ModelContainerSpec.Builder addGrpcPorts(int index, Port value)Immutable. List of ports to expose from the container. Vertex AI sends gRPC prediction requests that it receives to the first port on this list. Vertex AI also sends liveness and health checks to this port.
If you do not specify this field, gRPC requests to the container will be disabled.
Vertex AI does not use ports other than the first one listed. This field
corresponds to the ports field of the Kubernetes Containers v1 core API.
repeated .google.cloud.aiplatform.v1beta1.Port grpc_ports = 9 [(.google.api.field_behavior) = IMMUTABLE];
| Parameters | |
|---|---|
| Name | Description |
index | int |
value | Port |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | |
addGrpcPorts(int index, Port.Builder builderForValue)
public ModelContainerSpec.Builder addGrpcPorts(int index, Port.Builder builderForValue)Immutable. List of ports to expose from the container. Vertex AI sends gRPC prediction requests that it receives to the first port on this list. Vertex AI also sends liveness and health checks to this port.
If you do not specify this field, gRPC requests to the container will be disabled.
Vertex AI does not use ports other than the first one listed. This field
corresponds to the ports field of the Kubernetes Containers v1 core API.
repeated .google.cloud.aiplatform.v1beta1.Port grpc_ports = 9 [(.google.api.field_behavior) = IMMUTABLE];
| Parameters | |
|---|---|
| Name | Description |
index | int |
builderForValue | Port.Builder |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | |
addGrpcPortsBuilder()
public Port.Builder addGrpcPortsBuilder()Immutable. List of ports to expose from the container. Vertex AI sends gRPC prediction requests that it receives to the first port on this list. Vertex AI also sends liveness and health checks to this port.
If you do not specify this field, gRPC requests to the container will be disabled.
Vertex AI does not use ports other than the first one listed. This field
corresponds to the ports field of the Kubernetes Containers v1 core API.
repeated .google.cloud.aiplatform.v1beta1.Port grpc_ports = 9 [(.google.api.field_behavior) = IMMUTABLE];
| Returns | |
|---|---|
| Type | Description |
Port.Builder | |
addGrpcPortsBuilder(int index)
public Port.Builder addGrpcPortsBuilder(int index)Immutable. List of ports to expose from the container. Vertex AI sends gRPC prediction requests that it receives to the first port on this list. Vertex AI also sends liveness and health checks to this port.
If you do not specify this field, gRPC requests to the container will be disabled.
Vertex AI does not use ports other than the first one listed. This field
corresponds to the ports field of the Kubernetes Containers v1 core API.
repeated .google.cloud.aiplatform.v1beta1.Port grpc_ports = 9 [(.google.api.field_behavior) = IMMUTABLE];
| Parameter | |
|---|---|
| Name | Description |
index | int |
| Returns | |
|---|---|
| Type | Description |
Port.Builder | |
addPorts(Port value)
public ModelContainerSpec.Builder addPorts(Port value)Immutable. List of ports to expose from the container. Vertex AI sends any prediction requests that it receives to the first port on this list. Vertex AI also sends liveness and health checks to this port.
If you do not specify this field, it defaults to following value:
`json
[
{
"containerPort": 8080
}
]
Vertex AI does not use ports other than the first one listed. This field
corresponds to the ports` field of the Kubernetes Containers
v1 core
API.
repeated .google.cloud.aiplatform.v1beta1.Port ports = 5 [(.google.api.field_behavior) = IMMUTABLE];
| Parameter | |
|---|---|
| Name | Description |
value | Port |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | |
addPorts(Port.Builder builderForValue)
public ModelContainerSpec.Builder addPorts(Port.Builder builderForValue)Immutable. List of ports to expose from the container. Vertex AI sends any prediction requests that it receives to the first port on this list. Vertex AI also sends liveness and health checks to this port.
If you do not specify this field, it defaults to following value:
`json
[
{
"containerPort": 8080
}
]
Vertex AI does not use ports other than the first one listed. This field
corresponds to the ports` field of the Kubernetes Containers
v1 core
API.
repeated .google.cloud.aiplatform.v1beta1.Port ports = 5 [(.google.api.field_behavior) = IMMUTABLE];
| Parameter | |
|---|---|
| Name | Description |
builderForValue | Port.Builder |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | |
addPorts(int index, Port value)
public ModelContainerSpec.Builder addPorts(int index, Port value)Immutable. List of ports to expose from the container. Vertex AI sends any prediction requests that it receives to the first port on this list. Vertex AI also sends liveness and health checks to this port.
If you do not specify this field, it defaults to following value:
`json
[
{
"containerPort": 8080
}
]
Vertex AI does not use ports other than the first one listed. This field
corresponds to the ports` field of the Kubernetes Containers
v1 core
API.
repeated .google.cloud.aiplatform.v1beta1.Port ports = 5 [(.google.api.field_behavior) = IMMUTABLE];
| Parameters | |
|---|---|
| Name | Description |
index | int |
value | Port |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | |
addPorts(int index, Port.Builder builderForValue)
public ModelContainerSpec.Builder addPorts(int index, Port.Builder builderForValue)Immutable. List of ports to expose from the container. Vertex AI sends any prediction requests that it receives to the first port on this list. Vertex AI also sends liveness and health checks to this port.
If you do not specify this field, it defaults to following value:
`json
[
{
"containerPort": 8080
}
]
Vertex AI does not use ports other than the first one listed. This field
corresponds to the ports` field of the Kubernetes Containers
v1 core
API.
repeated .google.cloud.aiplatform.v1beta1.Port ports = 5 [(.google.api.field_behavior) = IMMUTABLE];
| Parameters | |
|---|---|
| Name | Description |
index | int |
builderForValue | Port.Builder |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | |
addPortsBuilder()
public Port.Builder addPortsBuilder()Immutable. List of ports to expose from the container. Vertex AI sends any prediction requests that it receives to the first port on this list. Vertex AI also sends liveness and health checks to this port.
If you do not specify this field, it defaults to following value:
`json
[
{
"containerPort": 8080
}
]
Vertex AI does not use ports other than the first one listed. This field
corresponds to the ports` field of the Kubernetes Containers
v1 core
API.
repeated .google.cloud.aiplatform.v1beta1.Port ports = 5 [(.google.api.field_behavior) = IMMUTABLE];
| Returns | |
|---|---|
| Type | Description |
Port.Builder | |
addPortsBuilder(int index)
public Port.Builder addPortsBuilder(int index)Immutable. List of ports to expose from the container. Vertex AI sends any prediction requests that it receives to the first port on this list. Vertex AI also sends liveness and health checks to this port.
If you do not specify this field, it defaults to following value:
`json
[
{
"containerPort": 8080
}
]
Vertex AI does not use ports other than the first one listed. This field
corresponds to the ports` field of the Kubernetes Containers
v1 core
API.
repeated .google.cloud.aiplatform.v1beta1.Port ports = 5 [(.google.api.field_behavior) = IMMUTABLE];
| Parameter | |
|---|---|
| Name | Description |
index | int |
| Returns | |
|---|---|
| Type | Description |
Port.Builder | |
addRepeatedField(Descriptors.FieldDescriptor field, Object value)
public ModelContainerSpec.Builder addRepeatedField(Descriptors.FieldDescriptor field, Object value)| Parameters | |
|---|---|
| Name | Description |
field | FieldDescriptor |
value | Object |
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | |
build()
public ModelContainerSpec build()| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec | |
buildPartial()
public ModelContainerSpec buildPartial()| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec | |
clear()
public ModelContainerSpec.Builder clear()| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | |
clearArgs()
public ModelContainerSpec.Builder clearArgs() Immutable. Specifies arguments for the command that runs when the container
starts. This overrides the container's
CMD. Specify
this field as an array of executable and arguments, similar to a Docker
CMD's "default parameters" form.
If you don't specify this field but do specify the
command
field, then the command from the command field runs without any
additional arguments. See the Kubernetes documentation about how the
command and args fields interact with a container's ENTRYPOINT and
CMD.
If you don't specify this field and don't specify the command field,
then the container's
ENTRYPOINT and
CMD determine what runs based on their default behavior. See the Docker
documentation about how CMD and ENTRYPOINT
interact.
In this field, you can reference environment variables
set by Vertex
AI
and environment variables set in the
env field. You
cannot reference environment variables set in the Docker image. In order
for environment variables to be expanded, reference them by using the
following syntax:
<code>$(<var>VARIABLE_NAME</var>)</code>
Note that this differs from Bash variable expansion, which does not use
parentheses. If a variable cannot be resolved, the reference in the input
string is used unchanged. To avoid variable expansion, you can escape this
syntax with $$; for example:
<code>$$(<var>VARIABLE_NAME</var>)</code>
This field corresponds to the args field of the Kubernetes Containers
v1 core
API.
repeated string args = 3 [(.google.api.field_behavior) = IMMUTABLE];
| Returns | |
|---|---|
| Type | Description |
ModelContainerSpec.Builder | This builder for chaining. |
clearCommand()
public ModelContainerSpec.Builder clearCommand() Immutable. Specifies the command that runs when the container starts. This
overrides the container's
ENTRYPOINT.
Specify this field as an array of executable and arguments, similar to a
Docker ENTRYPOINT's "exec" form, not its "shell" form.
If you do not specify this field, then the container's ENTRYPOINT runs,
in conjunction with the
args field or
the container's
CMD, if either
exists. If this field is not specified and the container does not have an
ENTRYPOINT, then refer to the Docker documentation about how CMD and
ENTRYPOINT
interact