Certain configuration settings can be set globally for Kubetorch, such as a unique username, default namespace, or installation url to use. More options to be added soon.
Username to use for Kubetorch deployments.
Used for authentication and resource naming. Will be validated to ensure Kubernetes compatibility.
License key for authentication and billing.
Required for usage reporting and cluster authentication. Can be found in the basic install guide.
Default queue name for scheduling services.
Controls how cluster resources are allocated and prioritized for services. See scheduling and queues for more info.
Default Kubernetes namespace for Kubetorch deployments.
All services will be deployed to this namespace unless overridden in the Compute resource constructor. If install_namespace is set, it will override this namespace.
Explicit override
Environment variable
File cache
In-cluster namespace or kubeconfig current context
Namespace for Kubetorch installation. Used for Kubetorch Cloud clients.
Explicit override
Environment variable
File cache
Default install namespace
URL of the Kubetorch version to install.
Used when installing Kubetorch in a Docker image or remote environment. Can be found in the basic install guide.
Whether to stream logs for Kubetorch services.
When enabled, logs from remote services are streamed back to your local environment
in real-time. Log level filtering can be controlled via LoggingConfig.level on the Compute.
Default is True
When disabled, logs remain accessible in-cluster but are not streamed to the client.
Note
Requires logging to be configured in the cluster (logStreaming.enabled: true` in the Helm chart)
Whether to stream metrics during execution of Kubetorch services.
When enabled, real-time CPU, memory, and GPU utilization metrics from remote Kubetorch services
are streamed back to the local environment for live monitoring.
Default is True.
When disabled, metrics are not collected.
Note
Requires monitoring to be configured in the cluster (metrics.enabled: true` in the Helm chart)
Cluster Config.
Default is {}.
Write out config to local ~/.kt/config.yaml, to be used globally.
values (optional) – Dict of key-value pairs to write/update in the filesystem. If provided, only these keys will be updated. None values will remove the key from the file.