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

feat: add otellogs.additionalDaemonSets configuration #2750

Merged
merged 14 commits into from
Jan 5, 2023

Conversation

sumo-drosiek
Copy link
Contributor

Description

Fill in your description here.


Checklist
  • Changelog updated
Testing performed
  • Redeploy fluentd and fluentd-events pods
  • Confirm events, logs, and metrics are coming in

Dominik Rosiek added 2 commits January 3, 2023 12:53
Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>
Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>
@sumo-drosiek sumo-drosiek requested a review from a team as a code owner January 4, 2023 07:25
@sumo-drosiek sumo-drosiek marked this pull request as draft January 4, 2023 07:25
Comment on lines +4305 to +4308
## additionalDaemonSets allows to set daemonsets with affinity, nodeSelector and resources
## different than the main DaemonSet
## Be careful and set nodeAffinity for the main DaemonSet,
## as we do not support multiple pods of otellogs on the same node
Copy link
Contributor Author

@sumo-drosiek sumo-drosiek Jan 4, 2023

Choose a reason for hiding this comment

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

@SumoLogic/open-source-collection-team

Do you think it is safe assumption that if customer needs to set it, thew will know how to do it properly?
Or could we limit configuration to nodeSelector and figure out nodeAffinities by ourselves?

Copy link

Choose a reason for hiding this comment

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

Let them figure it out imo, they should know what they're doing if they need to use this.

Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>
@andrzej-stencel
Copy link
Contributor

If we want to add this feature, we need to document it and provide examples. With proper documentation and the examples in place, I think we should be safe.

## operator: NotIn
## values:
## - linux
additionalDaemonSets: []
Copy link
Contributor

Choose a reason for hiding this comment

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

How about a map of named daemonsets? This might make it easier to use this feature, having a daemonset named e.g. otelcol-logs-collector-hpc instead of otelcol-logs-collector-1. Just a suggestion, it has its ins and outs (like making the names too long).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

this is actually a good idea. I will work on it

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

Dominik Rosiek added 2 commits January 4, 2023 12:59
Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>
…erent nodes

Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>
@github-actions github-actions bot added the documentation documentation label Jan 4, 2023
Dominik Rosiek added 2 commits January 4, 2023 14:45
Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>
Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>
@sumo-drosiek sumo-drosiek changed the title feat: add otellogs.additionDaemonSets confguration feat: add otellogs.additionDaemonSets configuration Jan 4, 2023
@sumo-drosiek sumo-drosiek changed the title feat: add otellogs.additionDaemonSets configuration feat: add otellogs.additionalDaemonSets configuration Jan 4, 2023
Dominik Rosiek and others added 2 commits January 4, 2023 15:14
Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>
@sumo-drosiek sumo-drosiek marked this pull request as ready for review January 4, 2023 14:30
Copy link

@swiatekm swiatekm left a comment

Choose a reason for hiding this comment

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

I'm not actually sure if this should be in best-practices, or maybe in troubleshooting instead?

docs/best-practices.md Outdated Show resolved Hide resolved
Co-authored-by: Mikołaj Świątek <mswiatek@sumologic.com>
@sumo-drosiek
Copy link
Contributor Author

I'm not actually sure if this should be in best-practices, or maybe in troubleshooting instead?

I think it could be in both

Dominik Rosiek added 4 commits January 5, 2023 08:58
Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>
Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>
Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>
Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>
@sumo-drosiek sumo-drosiek merged commit 5898acf into main Jan 5, 2023
@sumo-drosiek sumo-drosiek deleted the drosiek-multiple-collector-daemonsets branch January 5, 2023 09:35
@sumo-drosiek
Copy link
Contributor Author

false positive markdown link check (checked manually)

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

Successfully merging this pull request may close these issues.

3 participants