docs: Add Deploy a Pod page documenting On-Demand and Deploy When Available flows#664
Conversation
Documents the two Pod deployment paths (DOCS-450): Deploy On-Demand and Deploy When Available (Beta) for out-of-capacity GPUs. Adds the page to navigation and links it from the get-started Step 2 deploy step.
![promptless[bot]](https://avatars.githubusercontent.com/in/979718?s=60&v=4){kind=small}
| </Tab> | ||
| <Tab title="Deploy When Available"> | ||
| Use this path when the GPU you want is currently out of capacity. Runpod automatically deploys your Pod as soon as that GPU becomes available within your chosen time window. | ||
|
|
There was a problem hiding this comment.
Documented Deploy When Available as a Beta feature for out-of-capacity GPUs with email/in-console notifications and a configurable subscription window, based on DOCS-450 (which tracks CON-132, CON-152, and CON-10). The page body uses the customer's hand-corrected content pasted in the originating Slack thread after PR #662 was closed as incorrect.
Source: https://linear.app/runpod/issue/DOCS-450/ur-pod-experience-flow-update
There was a problem hiding this comment.
@Promptless instead of creatign a new page, can you add the details here - https://docs.runpod.io/get-started#step-2-deploy-a-pod page?
There was a problem hiding this comment.
@Promptless can you create tabs. Instead of Web create Deploy On-Demand and Deploy when available tabs and add the information. Update Deploy On-Demand tab with the latest instructions that I provided.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Address PR #664 review feedback: instead of a standalone pods/deploy-a-pod page, document the Deploy When Available (Beta) out-of-capacity flow inline in the get-started quickstart's Step 2. Remove the standalone page and revert its docs.json nav entry.
|
@lavanya-gunreddi good call — I've updated this PR to fold the Deploy On-Demand and Deploy When Available (Beta) content directly into the existing Step 2: Deploy a Pod section of the get-started page instead of creating a new standalone page. The new |
…lable tabs Per reviewer feedback on PR #664, replace the 'Web' tab in the get-started Step 2 section with two tabs — 'Deploy On-Demand' and 'Deploy When Available' — using the reviewer's corrected instructions. Content uses the Steps component to keep the page heading hierarchy clean. Terminal tab preserved.
|
@lavanya-gunreddi done — I've replaced the Web tab in the Step 2: Deploy a Pod section with two tabs: Deploy On-Demand and Deploy When Available, and folded in the latest instructions you provided. The Deploy On-Demand tab now reflects your corrected workload/compute/pricing/deploy steps, and the Deploy When Available (Beta) tab covers the out-of-capacity flow (All-tab selection, subscription modal, notifications, and subscription window). The existing Terminal tab is preserved. This is on the same docs PR #664 — ready for another look. |
- Rename 'Deploy On-Demand' tab to 'Deploy a Pod'; sentence-case 'Deploy when available' - Add early access / standard flow toggle inside the Deploy a Pod tab - Note Jupyter/SSH options appear only for official templates - Split region into its own step; document all four GPU tabs (Available, Recommended, All, Recent) - Use 'Sort by' dropdown; remove incorrect out-of-capacity alert - Add a storage step covering storage types and network volume selection behavior - Use 'persistent storage cost' and 'Deploy Pod' button label - Fix deploy-when-available flow: email selection (incl. team email), advanced scheduler meaning, insufficient-funds re-subscribe warning - Remove em-dashes and fix title-cased prose
Compare GPUs asks the Runpod assistant for a comparison rather than showing specs side by side, per reviewer feedback.
…o Deploy step - Rename 'Deploy a Pod' tab to 'Deploy via the console' and 'Terminal' to 'Deploy via the CLI' - Remove standalone 'Deploy when available' tab; add Deploy available Pod / Deploy when available tabs at the Deploy step of the Early access flow - Note out-of-capacity GPU selection in Select a GPU step, linking to the Deploy step
…rk volume filter description
1 participant
Open this suggestion in Promptless to view citations and reasoning process
Adds a standalone pods/deploy-a-pod page documenting the two Pod deployment paths — Deploy On-Demand and Deploy When Available (Beta) for out-of-capacity GPUs — using the customer's corrected content for Linear DOCS-450. Adds the page to navigation and links it from the get-started Step 2 deploy step.
Trigger Events
Tip: Worried about broken links? Ask Promptless to find and fix them automatically 🔗