Skip to content

Latest commit

 

History

History
19 lines (16 loc) · 5.38 KB

File metadata and controls

19 lines (16 loc) · 5.38 KB

ContainerGroupPatch

Represents a request to update a container group

Properties

Name Type Required Description
container UpdateContainer Represents an update container object
country_codes List[CountryCode] List of countries nodes must be located in. Remove this field to permit nodes from any country.
display_name str The display name for the container group. If null is provided, the display name will be set to the container group name.
liveness_probe ContainerGroupLivenessProbe Defines a liveness probe for container groups that determines when to restart a container if it becomes unhealthy
networking UpdateContainerGroupNetworking Represents update container group networking parameters
queue_autoscaler QueueBasedAutoscalerConfiguration Defines configuration for automatically scaling container instances based on queue length. The autoscaler monitors a queue and adjusts the number of running replicas to maintain the desired queue length.
readiness_probe ContainerGroupReadinessProbe Defines how to check if a container is ready to serve traffic. The readiness probe determines whether the container's application is ready to accept traffic. If the readiness probe fails, the container is considered not ready and traffic will not be sent to it.
replicas int The desired number of instances for your container group deployment.
scaling_actions List[ContainerGroupScalingAction] List of scaling actions configurations
scheduled_scaling_enabled bool Indicates if scheduled scaling is enabled
startup_probe ContainerGroupStartupProbe Defines a probe that checks if a container application has started successfully. Startup probes help prevent applications from being prematurely marked as unhealthy during initialization. The probe can use HTTP requests, TCP connections, gRPC calls, or shell commands to determine startup status.