-
Notifications
You must be signed in to change notification settings - Fork 150
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
Fix/persistent queue #668
Fix/persistent queue #668
Conversation
merge main from signalfx
# NOTE: The File Storage extension will persist state to the node's local file system. | ||
# While using the persistent queue it is advised to increase memory limit for agent (agent.resources.limits.memory) | ||
# to 1Gi. | ||
persistentQueueEnabled: |
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.
Does it make more sense to nest this in sendingQueue
since that's what uses it?
@@ -11,6 +11,11 @@ extensions: | |||
directory: {{ .Values.logsCollection.checkpointPath }} | |||
{{- end }} | |||
|
|||
{{- if or .Values.splunkPlatform.persistentQueueEnabled.logs .Values.splunkPlatform.persistentQueueEnabled.metrics }} |
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.
you defined the "splunk-otel-collector.persistentQueueEnabled"
template for this purpose
@@ -614,6 +619,9 @@ service: | |||
{{- if and (eq (include "splunk-otel-collector.logsEnabled" .) "true") (eq .Values.logsEngine "otel") }} | |||
- file_storage | |||
{{- end }} | |||
{{- if or .Values.splunkPlatform.persistentQueueEnabled.logs .Values.splunkPlatform.persistentQueueEnabled.metrics }} |
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.
same template note (there are other cases throughout)**
@@ -135,27 +135,39 @@ spec: | |||
imagePullPolicy: {{ .Values.image.initPatchLogDirs.pullPolicy }} | |||
command: ['sh', '-c', ' | |||
mkdir -p {{ .Values.logsCollection.checkpointPath }}; | |||
chown -Rv {{ $agent.securityContext.runAsUser | default 20000 }}:{{ $agent.securityContext.runAsGroup | default 20000 }} {{ .Values.logsCollection.checkpointPath }}; | |||
chown -Rv {{ $agent.securityContext.runAsUser | default 999 }}:{{ $agent.securityContext.runAsGroup | default 999 }} {{ .Values.logsCollection.checkpointPath }}; |
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 think this is a good change but could be problematic if users have adopted the 20000 id. Can you please add a breaking change note in the changelog?
chmod -v g+rwxs {{ .Values.logsCollection.checkpointPath }}; | ||
{{ if .Values.logsCollection.containers.enabled -}} | ||
if [ -d "/var/lib/docker/containers" ]; | ||
then | ||
setfacl -n -Rm d:m::rx,m::rx,d:g:{{ $agent.securityContext.runAsGroup | default 20000 }}:rx,g:{{ $agent.securityContext.runAsGroup | default 20000 }}:rx /var/lib/docker/containers; | ||
setfacl -n -Rm d:m::rx,m::rx,d:g:{{ $agent.securityContext.runAsGroup | default 999 }}:rx,g:{{ $agent.securityContext.runAsGroup | default 999 }}:rx /var/lib/docker/containers; |
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.
@wojtekzyla can you please make a separate PR for these changes? They seem unrelated and should be captured in a changelog separately. And please link an issue in that PR
Please rebase |
Things included in this PR: