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

Update to version 2.5.1 of the fluent-plugin-kubernetes_metadata_filter #92974

Merged
merged 2 commits into from Jul 16, 2020

Conversation

Ghazgkull
Copy link
Contributor

@Ghazgkull Ghazgkull commented Jul 10, 2020

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?:

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@k8s-ci-robot k8s-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Jul 10, 2020
@k8s-ci-robot
Copy link
Contributor

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.

@k8s-ci-robot k8s-ci-robot added cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Jul 10, 2020
@k8s-ci-robot
Copy link
Contributor

Welcome @Ghazgkull!

It looks like this is your first PR to kubernetes/kubernetes 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kubernetes has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jul 10, 2020
@k8s-ci-robot
Copy link
Contributor

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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

@k8s-ci-robot k8s-ci-robot added area/provider/gcp Issues or PRs related to gcp provider sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. release-note-none Denotes a PR that doesn't merit a release note. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Jul 10, 2020
@Ghazgkull
Copy link
Contributor Author

I signed it

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Jul 10, 2020
Copy link
Member

@monotek monotek left a 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

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jul 11, 2020
@k8s-ci-robot k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jul 11, 2020
Copy link
Member

@monotek monotek left a 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.

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 11, 2020
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 11, 2020
@Ghazgkull
Copy link
Contributor Author

Ghazgkull commented Jul 11, 2020

@monotek Thanks for the heads up. Image version bumped now.

@monotek
Copy link
Member

monotek commented Jul 12, 2020

/unhold

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 12, 2020
@Ghazgkull
Copy link
Contributor Author

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?

@Ghazgkull
Copy link
Contributor Author

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

@k8s-ci-robot
Copy link
Contributor

@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:

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

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.

@Ghazgkull
Copy link
Contributor Author

Ghazgkull commented Jul 12, 2020

/kind bug

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. and removed needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Jul 12, 2020
@Ghazgkull
Copy link
Contributor Author

@DirectXMan12 @kawych Can I please request help applying the required milestone tag?

@Ghazgkull
Copy link
Contributor Author

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?

@Ghazgkull
Copy link
Contributor Author

More noise... I realize now that the problem is that /lgtm was removed by the bot when I added the Makefile change it didn't get restored when @monotek re-approved the change.

@nikhita
Copy link
Member

nikhita commented Jul 14, 2020

@monotek can you re-apply lgtm?

/assign @onlydole
(release team lead) for applying the milestone

Copy link
Member

@monotek monotek left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 14, 2020
@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@justaugustus
Copy link
Member

/milestone v1.19

@k8s-ci-robot k8s-ci-robot added this to the v1.19 milestone Jul 15, 2020
@Ghazgkull
Copy link
Contributor Author

/retest

4 similar comments
@Ghazgkull
Copy link
Contributor Author

/retest

@Ghazgkull
Copy link
Contributor Author

/retest

@nikhita
Copy link
Member

nikhita commented Jul 16, 2020

/retest

@justaugustus
Copy link
Member

/retest

@k8s-ci-robot k8s-ci-robot merged commit 03509f3 into kubernetes:master Jul 16, 2020
@monotek
Copy link
Member

monotek commented Jul 16, 2020

I've just pushed the image to quay.io/fluentd_elasticsearch/fluentd:v3.0.3 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/provider/gcp Issues or PRs related to gcp provider cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error while watching pods: too old resource version with v2.4.5
6 participants