-
Notifications
You must be signed in to change notification settings - Fork 183
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
Conversation
Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>
Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>
## 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 |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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>
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. |
deploy/helm/sumologic/values.yaml
Outdated
## operator: NotIn | ||
## values: | ||
## - linux | ||
additionalDaemonSets: [] |
There was a problem hiding this comment.
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).
There was a problem hiding this comment.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>
…erent nodes 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>
deploy/helm/sumologic/templates/logs/collector/otelcol/daemonset.yaml
Outdated
Show resolved
Hide resolved
There was a problem hiding this 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?
Co-authored-by: Mikołaj Świątek <mswiatek@sumologic.com>
I think it could be in both |
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>
false positive markdown link check (checked manually) |
Description
Fill in your description here.
Checklist
Testing performed