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

expose cache params for enhance_k8s_metadata plugin #379

Merged
merged 10 commits into from Jan 30, 2020

Conversation

vsinghal13
Copy link
Contributor

@vsinghal13 vsinghal13 commented Jan 29, 2020

Description

Expose cache params for enhance_k8s_metadata plugin and change default cache size to 10000

Testing performed
  • ci/build.sh
  • Redeploy fluentd and fluentd-events pods
  • Confirm events, logs, and metrics are coming in

deploy/helm/sumologic/conf/metrics/metrics.conf Outdated Show resolved Hide resolved
deploy/helm/sumologic/values.yaml Outdated Show resolved Hide resolved
deploy/helm/sumologic/values.yaml Outdated Show resolved Hide resolved
Copy link
Contributor

@samjsong samjsong left a comment

Choose a reason for hiding this comment

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

I agree that these values should probably be controlled by the same config in the values.yaml file but it's a little confusing that they go under k8sMetadataFilter and reference the 3rd party plugin docs

though I suppose if we want to be minimally intrusive here, we don't have much of a choice but to keep them under k8sMetadataFilter :(

Copy link
Contributor

@frankreno frankreno left a comment

Choose a reason for hiding this comment

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

LGTM

@vsinghal13 vsinghal13 merged commit e05ccab into master Jan 30, 2020
@vsinghal13 vsinghal13 deleted the vsinghal-expose-metadata-cache-params branch January 30, 2020 00:33
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.

None yet

4 participants