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
Update to version 2.5.1 of the fluent-plugin-kubernetes_metadata_filter #92974
Conversation
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Welcome @Ghazgkull! |
Hi @Ghazgkull. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I signed 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.
/lgtm
/approve
/ok-to-test
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.
Sorry, I've just recognized you did not raised the image version in the makefile.
@monotek Thanks for the heads up. Image version bumped now. |
/unhold |
Thanks, @monotek. This is my first contribution to this project so I’m not 100% sure of the PR process here. Is there someone I should reach out to now to request this change be merged? |
The bots are saying this PR needs to be targetted to milestone v1.19. I'm assuming I don't have permission to do that myself? /milestone v1.19 |
@Ghazgkull: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/kind bug |
@DirectXMan12 @kawych Can I please request help applying the required milestone tag? |
Apologies for all the chatter. I'm new to the project here and trying to navigate the process for the first time. As an outsider, I don't have permission to actually view project membership (https://github.com/orgs/kubernetes/teams/milestone-maintainers/members gives me a 404), so I'm left groping in the dark. @coffeepac Looking through other PRs in this area, I see your approvals appearing before the bot adds the v1.19 milestone label. So I'm speculating that you might be the approval I need? |
More noise... I realize now that the problem is that |
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
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Ghazgkull, 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 |
/milestone v1.19 |
/retest |
4 similar comments
/retest |
/retest |
/retest |
/retest |
I've just pushed the image to quay.io/fluentd_elasticsearch/fluentd:v3.0.3 :) |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Updates to version 2.5.1 of the fluent-plugin-kubernetes_metadata_filter plugin. This version of the plugin contains a change to address the problem of unhandled "410 Gone" errors during the plugin's pod watch. (See fabric8io/fluent-plugin-kubernetes_metadata_filter#243)
Which issue(s) this PR fixes:
Fixes fabric8io/fluent-plugin-kubernetes_metadata_filter#226
Special notes for your reviewer:
@monotek I originally reported this defect to the fluentd-elasticsearch helm chart a couple months back and you thankfully rolled back to an earlier version in order to avoid this bug: kiwigrid/helm-charts#340 (comment)
I jumped in and contributed a fix to the kubernetes metadata filter plugin which is now available in this release.
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: