Skip to content

Runpod: fix registry_auth support#3844

Merged
un-def merged 1 commit into
masterfrom
issue_3843_fix_runpod_registry_auth
May 5, 2026
Merged

Runpod: fix registry_auth support#3844
un-def merged 1 commit into
masterfrom
issue_3843_fix_runpod_registry_auth

Conversation

@un-def

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

Copy link
Copy Markdown
Collaborator

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
@un-def un-def merged commit 9115030 into master May 5, 2026
25 checks passed
@un-def un-def deleted the issue_3843_fix_runpod_registry_auth branch May 5, 2026 06:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants