Skip to content

fix: kubernetes imagePullSecrets support for argo workflows #2494

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 15, 2025

Conversation

saikonen
Copy link
Collaborator

Argo workflows does not support applying imagePullSecrets on a per-template basis, only on a workflow template level.

Changing the implementation to leverage podSpecPatch in order to apply the imagePullSecrets on a per task basis

JobSets were not tested but should be unaffected due to them utilizing create within the spec and simply dumping native k8s job specs

closes #2477

@saikonen saikonen requested a review from savingoyal July 15, 2025 22:08
@savingoyal savingoyal merged commit 51a8d3f into master Jul 15, 2025
28 checks passed
@savingoyal savingoyal deleted the fix/image-pull-secrets-on-argo branch July 15, 2025 22:09
valayDave pushed a commit to valayDave/metaflow that referenced this pull request Jul 21, 2025
fix: kubernetes imagePullSecrets support for argo workflows

Argo workflows does not support applying imagePullSecrets on a
per-template basis, only on a workflow template level.

Changing the implementation to leverage podSpecPatch in order to apply
the imagePullSecrets on a per task basis

JobSets were not tested but should be unaffected due to them utilizing
`create` within the spec and simply dumping native k8s job specs

WILL BE Removed after releasing 2.16+
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.

Kubernetes image pull secret feature not taking effect
2 participants