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

Updated chart with support for cache_refresh_apiserver_request_delay #1974

Merged
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions deploy/helm/sumologic/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -68,6 +68,7 @@ The following table lists the configurable parameters of the Sumo Logic chart an
| `fluentd.metadata.cacheTtl` | Option to control the enabling of metadata filter plugin cache_ttl (in seconds). | `7200` |
| `fluentd.metadata.cacheRefresh` | Option to control the interval at which metadata cache is asynchronously refreshed (in seconds). | `3600` |
| `fluentd.metadata.cacheRefreshVariation` | Option to control the variation in seconds by which the cacheRefresh option is changed for each pod separately. For example, if cache refresh is 1 hour and variation is 15 minutes, then actual cache refresh interval will be a random value between 45 minutes and 1 hour 15 minutes, different for each pod. This helps spread the load on API server that the cache refresh induces. Setting this to 0 disables cache refresh variation. | `900` |
| `fluentd.metadata.cache_refresh_apiserver_request_delay` | Option to control the delay with which cache refresh calls hit the api server.For example, if 0 then all metadata enrichment happen immediately. Setting this to a non-zero values ensures the traffic to api server is much distributed. | `0` |
gizmo-rt marked this conversation as resolved.
Show resolved Hide resolved
| `fluentd.metadata.pluginLogLevel` | Option to give plugin specific log level. | `error` |
| `fluentd.logs.enabled` | Flag to control deploying the Fluentd logs statefulsets. | `true` |
| `fluentd.logs.statefulset.nodeSelector` | Node selector for Fluentd log statefulset. | `{}` |
Expand Down
1 change: 1 addition & 0 deletions deploy/helm/sumologic/conf/metrics/fluentd/metrics.conf
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,7 @@
cache_ttl {{ .Values.fluentd.metadata.cacheTtl | quote }}
cache_refresh {{ .Values.fluentd.metadata.cacheRefresh | quote }}
cache_refresh_variation {{ .Values.fluentd.metadata.cacheRefreshVariation | quote }}
cache_refresh_apiserver_request_delay {{ .Values.fluentd.metadata.cache_refresh_apiserver_request_delay | quote }}
gizmo-rt marked this conversation as resolved.
Show resolved Hide resolved
core_api_versions {{ join "," .Values.fluentd.metadata.coreApiVersions }}
api_groups {{ join "," .Values.fluentd.metadata.apiGroups }}
</filter>
Expand Down
5 changes: 5 additions & 0 deletions deploy/helm/sumologic/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -317,6 +317,11 @@ fluentd:
## will be a random value between 45 minutes and 1 hour 15 minutes, different for each pod. This helps spread
## the load on API server that the cache refresh induces. Setting this to 0 disables cache refresh variation.
cacheRefreshVariation: "900"
# Option to control the delay with which cache refresh calls hit the api server.
# For example, if 0 then all metadata enrichment happen immediately. Setting this to a non-zero values ensures the
# traffic to api server is much distributed.
# Disclaimer: Not recommended for use, if your api server read latency is > 1s
cache_refresh_apiserver_request_delay: "0"
gizmo-rt marked this conversation as resolved.
Show resolved Hide resolved
## Option to give plugin specific log level
pluginLogLevel: "error"
## Option to specify K8s API versions
Expand Down