-
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
Bump versions of plugins used in Dockerfile #121
Conversation
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.
One question, rest lgtm
@@ -179,7 +179,6 @@ data: | |||
cache_size "#{ENV['K8S_METADATA_FILTER_BEARER_CACHE_SIZE']}" | |||
cache_ttl "#{ENV['K8S_METADATA_FILTER_BEARER_CACHE_TTL']}" | |||
tag_to_kubernetes_name_regexp '.+?\.containers\.(?<pod_name>[^_]+)_(?<namespace>[^_]+)_(?<container_name>.+)-(?<docker_id>[a-z0-9]{64})\.log$' | |||
merge_json_log false |
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.
Why do need to remove this one?
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 parameter was removed in the newer version of kubernets_metadata
plugin, from their README:
NOTE: As of the release 2.1.x of this plugin, it no longer supports parsing the source message into JSON and attaching it to the payload. The following configuration options are removed:
merge_json_log
preserve_json_log
@@ -17,14 +17,13 @@ RUN apk add --no-cache --update --virtual .build-deps sudo build-base ruby-dev \ | |||
&& gem install snappy | |||
|
|||
# FluentD plugins from RubyGems | |||
RUN gem install fluent-plugin-s3 -v 1.1.4 \ |
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.
is this plugin not being used anywhere so we are removing 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.
It's not being used currently, but after talking with Frank we want to keep it around in case a customer wants to fork their data to S3 (and in the future GCP, Azure, etc.).
548968e
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.
LGTM
* Test if deleting fixes plan output * Remove dummy file * Test if deleting roles fixes plan output
Noticed several of our fluentd plugin gems are out of date, and one is not being used.
Testing performed:
FYI: @lei-sumo @frankreno