Manage Runpod as code with Terraform provider 2.0

Runpod’s Terraform provider enables infrastructure-as-code management of Pods, Serverless endpoints, templates, volumes, Instant Clusters, and registry credentials alongside other cloud resources, with plans allowing changes to be reviewed before billable infrastructure is created. Provider 2.0, released in October, is generated from Runpod’s REST v2 API and standardizes attributes around documented API fields, but it is a breaking upgrade from 1.x, which relies on the retiring REST v1 API. Users need Terraform 1.6 or later and are advised to authenticate through the RUNPOD_API_KEY environment variable rather than storing keys in configuration or state files. A quickstart example creates a GPU Pod with PyTorch, SSH, Jupyter, exposed ports, and outputs for its ID and status, while emphasizing that running Pods incur per-minute charges and should be destroyed or stopped when no longer needed. The provider can also be used with AI agents to draft plans, though users should review plans before approving deployment and keep credentials outside prompts. Migrating from 1.x requires updating configurations, recording resource IDs, renaming certain resources, removing and re-importing affected state entries, and carefully reviewing replacements, particularly for Pods whose replacement can permanently delete local data.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.