Skip to content

feat: Add support for DataDog Extended Daemonset #71

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

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

F28956
Copy link

@F28956 F28956 commented Apr 11, 2025

DataDog Extended Daemonset

ExtendedDaemonSet aims to provide a new implementation of the Kubernetes DaemonSet resource with key features:

  • Canary Deployment: Deploy a new DaemonSet version with only a few nodes.
  • Custom Rolling Update: Improve the default rolling update logic available in Kubernetes batch/v1 Daemonset.

Managing Taints for DataDog Extended Daemonset to nidhogg allows ensuring that DataDog Agent is up and ready to accept connections from applications deployed on the same node (when DataDog Agent is configured to use Extended Daemonsets).

F28956 and others added 4 commits April 11, 2025 10:26
[DataDog Extended Daemonset](https://github.com/DataDog/extendeddaemonset)

ExtendedDaemonSet aims to provide a new implementation of the Kubernetes DaemonSet resource with key features:

* Canary Deployment: Deploy a new DaemonSet version with only a few nodes.
* Custom Rolling Update: Improve the default rolling update logic available in Kubernetes batch/v1 Daemonset.

Managing Taints for DataDog Extended Daemonset to nidhogg allows
ensuring that DataDog Agent is up and ready to accept connections from
applications deployed on the same node (when DataDog Agent is configured
to use Extended Daemonsets).
@josmo
Copy link
Member

josmo commented Jun 8, 2025

Thanks for the PR @F28956 and sorry for not responding/looking at this sooner. We're planning on looking at this soon for any potential feedback and what not to have a path to merge this in.

@F28956
Copy link
Author

F28956 commented Jun 8, 2025

Thanks @josmo for looking into this, apretiate any feedback.

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