From 1feb9ee969eaa114f66df66661d6f0bae560a536 Mon Sep 17 00:00:00 2001 From: "promptless[bot]" Date: Thu, 27 Aug 2026 23:01:48 +0000 Subject: [PATCH] Remove --stop-after and --terminate-after from runpodctl pod create reference These flags were removed from the CLI in runpod/runpodctl#330 because they were forwarded to the API but never enforced. Passing either now errors. --- runpodctl/reference/runpodctl-pod.mdx | 8 -------- 1 file changed, 8 deletions(-) diff --git a/runpodctl/reference/runpodctl-pod.mdx b/runpodctl/reference/runpodctl-pod.mdx index 3ae1c05b4..9b2bef921 100644 --- a/runpodctl/reference/runpodctl-pod.mdx +++ b/runpodctl/reference/runpodctl-pod.mdx @@ -184,14 +184,6 @@ Container registry authentication ID for pulling private images. Use [`runpodctl Country code for regional deployment (e.g., `US`, `CA`, `EU`). Restricts Pod placement to machines in the specified region. - -Automatically stop the Pod after the specified duration (e.g., `1h`, `24h`, `7d`). - - - -Automatically terminate the Pod after the specified duration (e.g., `1h`, `24h`, `7d`). Unlike `--stop-after`, this permanently deletes the Pod. - - Compliance settings for the Pod (e.g., regulatory requirements for data handling).