updated fluentd to 1.2.4

[monotek]

What this PR does / why we need it:

• updates fluentd in fluentd-elasticsearch to version 1.2.4
• also updates activesupport, fluent-plugin-elasticsearch & oj gems

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Release note:

* updates fluentd in fluentd-elasticsearch to version 1.2.4
* also updates activesupport, fluent-plugin-elasticsearch & oj gems

[yue9944882]

/cc dixudx

[monotek]

/assign @coffeepac

[neolit123]

@monotek
please add a release note.
/ok-to-test

[monotek]

release notes added...

[coffeepac]

/approve
/retest

[dixudx]

/lgtm

Please update cluster/addons/fluentd-elasticsearch/fluentd-es-ds.yaml accordingly to use latest v2.3.0 after this PR gets merged.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: coffeepac, dixudx, monotek

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• cluster/addons/fluentd-elasticsearch/OWNERS [coffeepac]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-github-robot]

Automatic merge from submit-queue (batch tested with PRs 64445, 67459, 67434). If you want to cherry-pick this change to another branch, please follow the instructions here.

[monotek]

@coffeepac

Seems theres is still no automatic build of the image:

https://console.cloud.google.com/gcr/images/google-containers/GLOBAL/fluentd-elasticsearch?gcrImageListsize=50

Are these build jobs available in a repo, where i can contribute?
If so, where?

[coffeepac]

nope. this is a google-internal image. Its on my list to make it not that. I'll file an issue against myself so I stop letting it fall off my list.

[aleks-mariusz]

any ideas when this will be generally available publicly to start using ?

[coffeepac]

@aleks-mariusz I'm waiting for #67484 (comment) to get merged before I ask a googler to build. they can kick both jobs off at once. after that it will take ~24 hours.

Due to team geography (Ie: they're sleeping soon) I expect this will take ~36 hours

[aleks-mariusz]

cool, but i saw a typo in that issue (the first part of the commit has 6.3.2 but the second has 6.3.0).. made a mention of this on that issue as well.

[coffeepac]

@aleks-mariusz available now, though its v2.3.1 . v2.3.0 wasn't built.

[neolit123]

/sig instrumentation