Skip to content

deployment instead of daemonset? #2

@dcherman

Description

@dcherman

the usage of a daemonset is no longer strictly necessary. originally, the daemonset was used in order to add labels to individual pods for use with podAffinity in order to have argo target nodes that already had the images pre-pulled, however that's actually already a factor in the kubernetes scheduler algo

we can swap to using a deployment instead and reduce the number of controller pods that we need down to 1, although we would need to add privileges to get/list/watch nodes, and we lose the ability to target specific nodes for image pre-pulling which could be implemented taints/tolerations/nodeSelector on the daemonset right now.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions