Skip to content
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

feature: run heartbeat with Argo daemon containers #1916

Merged
merged 12 commits into from
Jul 30, 2024

Conversation

saikonen
Copy link
Collaborator

@saikonen saikonen commented Jul 8, 2024

Introducing run heartbeat updates as an argo daemon container to decouple workflow status from the active workflow pod health.

@saikonen saikonen changed the title wip: Argo Daemon containers feature: run heartbeat with Argo daemon containers Jul 8, 2024
Copy link
Collaborator

@savingoyal savingoyal left a comment

Choose a reason for hiding this comment

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

LGTM!

metaflow/plugins/argo/argo_workflows.py Show resolved Hide resolved
metaflow/plugins/argo/argo_workflows.py Outdated Show resolved Hide resolved
@@ -846,6 +846,8 @@ def _compile_workflow_template(self):
.templates(self._container_templates())
# Exit hook template(s)
.templates(self._exit_hook_templates())
# Sidecar templates (Daemon Containers)
.templates(self._daemon_container_templates())
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can we make this optional through the cli - —with-daemon-container/—no-with-daemon-container ? That way folks can opt out if needed

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

done. One thought on the wording for the toggle though: Currently we only run heartbeats, and in the future some other run-scope-processes in the default container.

what happens with the toggle though, if we introduce a way for users to launch their own daemon containers alongside tasks? should these also not deploy if --no-with-daemon-container is specified, or should it not apply to user defined ones?

savingoyal
savingoyal previously approved these changes Jul 30, 2024
@savingoyal savingoyal merged commit fefc2db into master Jul 30, 2024
25 checks passed
@savingoyal savingoyal deleted the feature/argo-daemon-containers branch July 30, 2024 22:12
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.

2 participants