You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 7, 2026. It is now read-only.
Repository navigation
Commit 7dee48c
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/reference/config.md
-12Lines changed: 0 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,18 +108,6 @@ You can configure Vivaria to run task environments and agent containers in:
108
108
|`VIVARIA_AWS_ACCESS_KEY_ID_FOR_EKS`| If using EKS, an AWS access key ID for an IAM user with permission to create and delete Pods in the EKS cluster. |
109
109
|`VIVARIA_AWS_SECRET_ACCESS_KEY_FOR_EKS`| If using EKS, the AWS secret access key for the IAM user with permission to create and delete Pods in the EKS cluster. |
|`VIVARIA_K8S_GPU_CLUSTER_URL`| The URL of the Kubernetes cluster with GPUs used by Vivaria. |
116
-
|`VIVARIA_K8S_GPU_CLUSTER_CA_DATA`| Vivaria uses this to verify the Kubernetes cluster's identity, to prevent man-in-the-middle attacks. Vivaria puts this in the cluster's `certificate-authority-data` field in its kubeconfig object. |
117
-
|`VIVARIA_K8S_GPU_CLUSTER_NAMESPACE`| The namespace in the Kubernetes cluster with GPUs where Vivaria will create resources. Defaults to 'default'. |
118
-
|`VIVARIA_K8S_GPU_CLUSTER_IMAGE_PULL_SECRET_NAME`| If you're pulling images from a private registry, put credentials for the registry in a Kubernetes secret as specified here: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/ Then, set this to the name of the secret. |
119
-
|`VIVARIA_K8S_GPU_CLUSTER_CLIENT_CERTIFICATE_DATA`| The client certificate for the Kubernetes cluster with GPUs. Vivaria puts this in the `client-certificate-data` field of the user it uses to authenticate to the cluster. |
120
-
|`VIVARIA_K8S_GPU_CLUSTER_CLIENT_KEY_DATA`| The client key for the Kubernetes cluster with GPUs. Vivaria puts this in the `client-key-data` field of the user it uses to authenticate to the cluster. |
121
-
|`VIVARIA_API_IP_FOR_K8S_GPU_CLUSTER`| An IP address or hostname at which pods in the Kubernetes cluster with GPUs can find the Vivaria server. |
// environment variables. It should include a list of host configs and each host config should have an API IP.
214
205
if(hostinstanceofK8sHost){
215
206
switch(host.machineId){
216
-
caseK8S_GPU_HOST_MACHINE_ID:
217
-
returnthis.VIVARIA_API_IP_FOR_K8S_GPU_CLUSTER??throwErr('VIVARIA_API_IP_FOR_K8S_GPU_CLUSTER not set')
218
207
caseK8S_HOST_MACHINE_ID:
219
208
returnthis.API_IP??throwErr('API_IP not set')
220
209
default:
@@ -313,7 +302,7 @@ class RawConfig {
313
302
assertHasGpuSupport(): void{
314
303
if(this.gpuMode===GpuMode.NONE){
315
304
thrownewError(
316
-
`Task requires GPUs but this Vivaria instance doesn't support them: MP4_DOCKER_USE_GPUS and ENABLE_VP are both falsy, and at least one of VIVARIA_K8S_GPU_CLUSTER_URL and VIVARIA_K8S_GPU_CLUSTER_CA_DATA is not set.`,
305
+
`Task requires GPUs but this Vivaria instance doesn't support them: MP4_DOCKER_USE_GPUS and ENABLE_VP are both falsy.`,
0 commit comments