Skip to content

docs: Document Pod experience updates: Deploy When Available, savings plan discontinuation, Recommended/NVLink, Pod inspector#662

Closed
promptless[bot] wants to merge 1 commit into
mainfrom
promptless/pod-experience-flow-updates
Closed

docs: Document Pod experience updates: Deploy When Available, savings plan discontinuation, Recommended/NVLink, Pod inspector#662
promptless[bot] wants to merge 1 commit into
mainfrom
promptless/pod-experience-flow-updates

Conversation

@promptless

@promptless promptless Bot commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Open this suggestion in Promptless to view citations and reasoning process

Documents Pod experience features from Console Experience cycles 1–2 (Linear DOCS-450): Deploy When Available for out-of-capacity GPUs, Recommended tab behavior, NVLink availability banner, savings plan discontinuation, and the Pod inspector "Template details" rename plus "Report problem" feedback button.

Trigger Events


Tip: Tell your friends working on non-commercial open-source projects to apply for free Promptless access at promptless.ai/oss ❤️

- Deploy When Available, Recommended tab, and NVLink banner in choose-a-pod
- Deploy When Available tip in get-started quickstart
- Savings plan discontinuation notice; remove active creation framing
- Pod inspector: Template details rename + Report problem button
- June 2026 product update entry
Comment thread pods/choose-a-pod.mdx

When you deploy a multi-GPU Pod (a GPU count greater than 1) on an H100, H200, or B200, a banner tells you whether the GPU supports NVLink. Only SXM and NVL cards provide NVLink for high-bandwidth GPU-to-GPU communication, which benefits distributed training and other workloads that exchange large amounts of data between GPUs.

### Deploy when available

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Documented the Deploy when available window options from CON-152: clicking the Now or In 24 hours block opens a calendar selector with hour/minute precision, and 24 hours is the default. CON-132 establishes the feature exists for out-of-capacity GPUs with email + inbox notifications.

Source: https://linear.app/runpod/issue/CON-152/update-deploy-when-available-from-and-to-ux

Comment thread pods/choose-a-pod.mdx

When your chosen GPU is out of capacity, you don't have to deploy immediately or keep retrying. Select **Deploy When Available** to queue your Pod, and Runpod deploys it automatically as soon as the GPU frees up.

You set a window for when Runpod should attempt the deployment:

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sourced the email + console inbox notification "when your Pod deploys or finishes migrating" from CON-10 (notify when a Pod becomes available during migrations) combined with CON-132's email + inbox notification support.

Source: https://linear.app/runpod/issue/CON-10/notify-when-a-pod-becomes-available-during-migrations

Comment thread pods/choose-a-pod.mdx

When you deploy a Pod, the deploy screen surfaces a few features that help you find available capacity and choose the best GPU for your workload.

### Recommended tab

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Described the Recommended tab behavior from CON-34: it shows the template's recommended GPUs first, then adds up to three additional available GPUs ranked by VRAM (stockStatus not null) that aren't already recommended.

Source: https://linear.app/runpod/issue/CON-34/show-high-availability-options-in-recommended

Comment thread pods/choose-a-pod.mdx

The **Recommended** tab highlights the GPUs best suited to your selected template. It lists the template's recommended GPUs first, then adds up to three more GPUs that are currently available, ranked by VRAM. This lets you compare strong recommendations against options that are in stock and ready to deploy right away.

### NVLink availability

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sourced the NVLink availability banner for multi-GPU deploys (GPU count > 1) on H100/H200/B200, and that only SXM and NVL cards support NVLink, from CON-9 acceptance criteria and Greg Wester's note that "NVL and SXM are advertisements for nvlink."

Source: https://linear.app/runpod/issue/CON-9/show-nvlink-availability-for-multi-gpu-pod-deploys

Comment thread pods/pricing.mdx

<Warning>
Savings plans only cover GPU compute costs—[storage costs](/pods/storage/types) are billed at standard rates. Storage charges continue to accrue on stopped Pods. If your balance reaches \$0, your Pods stop: those with a network volume are preserved, while those without one are terminated and their data cannot be recovered. Plans are non-refundable and have fixed expiration dates.
Savings plans have been discontinued. You can no longer create new savings plans, but existing plans are unaffected and remain active until their commitment period expires.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rewrote the Savings plans section as a discontinuation notice per CON-171: savings plan creation is being hidden/disabled while existing plans remain unaffected and run to expiration (~300 affected users notified by email).

Source: https://linear.app/runpod/issue/CON-171/discontinue-savings-plans

Comment thread pods/manage-pods.mdx

Access logs from the [Pods page](https://www.console.runpod.io/pods) by expanding your Pod and clicking **Logs**.

## View template details

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added the View template details section from CON-108: in the Pod inspector, "Template readme" was renamed to "Template details" and a "Report problem with template" button was added that opens an open-ended feedback modal.

Source: https://linear.app/runpod/issue/CON-108/add-template-feedback-inside-the-pod-details

@mintlify

mintlify Bot commented Jun 17, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
runpod-docs 🟢 Ready View Preview Jun 17, 2026, 4:28 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants