Skip to content
This repository has been archived by the owner on Aug 10, 2019. It is now read-only.

Suggestion: move to DaemonSet deployments for tasks required on every node #118

Closed
Waterdrips opened this issue Jun 11, 2019 · 2 comments
Closed

Comments

@Waterdrips
Copy link
Contributor

No description provided.

@Waterdrips
Copy link
Contributor Author

Hi,

You mentioned at the Craft Conf talk that the deployments are not managed as a deamonset.
It might be good to deploy them in this way so you can guarantee every node gets 1 set of the application components.

Kubernetes docs on DaemonSets : https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/

@Waterdrips Waterdrips changed the title Suggestion: Suggestion: move to DaemonSet deployments for tasks required on every node Jun 11, 2019
@vsreekanti
Copy link
Member

Thanks for pointing this out, @Waterdrips. It looks like DaemonSets simplify a lot of the deployment challenges we've had. Thanks for pointing this out! I'm working on moving to this model right now. 😄

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants