-
Notifications
You must be signed in to change notification settings - Fork 39.8k
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 fluentd to 1.2.4 #67434
updated fluentd to 1.2.4 #67434
Conversation
/cc dixudx |
/assign @coffeepac |
@monotek |
release notes added... |
/approve |
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
Please update cluster/addons/fluentd-elasticsearch/fluentd-es-ds.yaml
accordingly to use latest v2.3.0 after this PR gets merged.
[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:
Approvers can indicate their approval by writing |
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. |
Seems theres is still no automatic build of the image: Are these build jobs available in a repo, where i can contribute? |
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. |
any ideas when this will be generally available publicly to start using ? |
@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 |
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. |
@aleks-mariusz available now, though its v2.3.1 . v2.3.0 wasn't built. |
/sig instrumentation |
What this PR does / why we need it:
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: