Dev Pod Configurations

When creating a dev pod, you can configure the resource, container and more options for it.

Resource

Node Group: First you need to select one or more node groups to determine what resources this pod can use from.
Priority: Set the priority of the pod, defaults to Medium(4). If the specified node group has limited resources, you can set the priority accordingly to get higher priority resource allocation.
Resource shape: The instance type that the pod will be running on. Select from a variety of CPU and GPU shapes. Refer to Node Group Shapes for more details.
Nodes: Default to no specific nodes, but you can specify the nodes you want to launch the pod on.
Can preempt lower priority workload: Whether the pod can preempt lower priority workload, defaults to false.
Can be preempted by higher priority workload: Whether the pod can be preempted by higher priority workload, defaults to false.

Image: The container image that will be used to create the pod. You can choose from the default image lists or use your own custom image.
SSH Public Key: The SSH public key that will be used to access the pod, only available for default images with Dev Pod entrypoint, refer to this guide for more details.
Enable JupyterLab: Whether to enable JupyterLab in the pod, defaults to false. Only available for default images with Dev Pod entrypoint, refer to this guide for more details.
Private image registry auth (optional): If you are using a private image, you need to specify the image registry auth.
Entrypoint(Run Command): Entrypoint of the Dev Pod container, you can choose from the following options:
- Dev Pod entrypoint: Automatically applies a run command based on the selected image.
- Image default entrypoint: Uses the image's default run command.
- Custom entrypoint: Specify a custom entrypoint for the container. This will override the default entrypoint.
Run as: When using a custom image, you can choose to run the container as root or image default user. Defaults to image default user.

Mount storage for the pod container, refer to this guide for more details.

Log Collection: Whether to collect the logs from the container, following the workspace level setting by default.
Shared Memory: The size of the shared memory that will be allocated to the container.
Archive time: The time to keep the job's logs and artifacts after the job is completed, defaults to 3 days.
Visibility: Specifies the visibility of the job. If set to private, only the creator can access the job. If set to public, all users in the workspace can access the job.
Environment Variables: Environment variables are key-value pairs that are passed to the pod container, so the runtime can refer to them as needed.