Skip to content

Runpod: fix registry_auth support#3844

Open
un-def wants to merge 1 commit intomasterfrom
issue_3843_fix_runpod_registry_auth
Open

Runpod: fix registry_auth support#3844
un-def wants to merge 1 commit intomasterfrom
issue_3843_fix_runpod_registry_auth

Conversation

@un-def
Copy link
Copy Markdown
Collaborator

@un-def un-def commented May 1, 2026

For individual pods (single-node runs), set containerRegistryAuthId when a pod is created. All three mutations support this (undocumented) parameter:

  • podFindAndDeployOnDemand (gpu, on-demand)
  • podRentInterruptable (gpu, spot)
  • deployCpuPod (cpu, on-demand; the mutation itself is undocumented)

For clusters, continue to use podEditJob workaround, but update only containerRegistryAuthId, other fields are optional (contrary to the spec, which is indeed outdated).

Fixes: #3843

For individual pods (single-node runs), set containerRegistryAuthId
when a pod is created. All three mutations support this (undocumented)
parameter:

* podFindAndDeployOnDemand (gpu, on-demand)
* podRentInterruptable (gpu, spot)
* deployCpuPod (cpu, on-demand; the mutation itself is undocumented)

For clusters, continue to use podEditJob workaround, but update
only containerRegistryAuthId, other fields are optional (contrary to the
spec, which is indeed outdated).

Fixes: #3843
@un-def un-def requested a review from jvstme May 1, 2026 16:09
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.

[Bug]: Runpod: pod won't start if registry_auth is specified

1 participant