Feature Request
The RunPod GraphQL API allows querying and terminating pods but does not expose the full launch configuration needed to programmatically create pods — specifically:
- Container disk size
- GPU type selection
- Docker image / template selection
This forces users to use the web UI for pod creation even in fully automated training workflows. Querying status and terminating pods works great, but without launch support the API is only half useful for MLOps pipelines.
Expected Behavior
All pod launch parameters available in the web UI should be exposed through the GraphQL API so pods can be created, configured, and launched programmatically without any manual web UI interaction.
Current Workaround
Manual web UI launch required for every new training run.
Feature Request
The RunPod GraphQL API allows querying and terminating pods but does not expose the full launch configuration needed to programmatically create pods — specifically:
This forces users to use the web UI for pod creation even in fully automated training workflows. Querying status and terminating pods works great, but without launch support the API is only half useful for MLOps pipelines.
Expected Behavior
All pod launch parameters available in the web UI should be exposed through the GraphQL API so pods can be created, configured, and launched programmatically without any manual web UI interaction.
Current Workaround
Manual web UI launch required for every new training run.