-
Notifications
You must be signed in to change notification settings - Fork 38.9k
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
Collect pod log in fluentd-gcp #74502
Conversation
The Fluentd config we use for GKE has been pulled to an internal repo. The OSS version here is only there for legacy gke_container monitored resource. Started a conversation internally for the next steps. |
3d2fe3d
to
1283d60
Compare
1283d60
to
f4cf2a3
Compare
Discussed offline. We still need this to support GCE Kubernetes users. |
Code freeze for 1.14 is coming up in 2 days. This PR is fairly new and needs some reviews. Can we punt this PR to 1.15? |
/hold 1.14 enhancement lead here - given this is a new PR and it's large and we've passed code freeze do we want this PR in the 1.14 release? I see an unanswered question about this above |
f4cf2a3
to
7ffa7da
Compare
Drop the fluentd update based on #74502 (comment).
This is a GCE specific small change. Can we still make it in 1.14? It will be reviewed today. |
@claurence I scoped down the change. And it is GCP specific that won't affect anyone else. :) |
The change itself looks good. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Random-Liu, yujuhong 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 |
/test pull-kubernetes-e2e-gce |
@nikopen @spiffxp given this change is now de-scoped to only impact GCP any concerns from y'alls perspective as bug triage and release lead around it landing in 1.14? There are two failing jobs which @Random-Liu is looking into. |
@claurence this PR is not related to let's say 'core K8S' at all, so it's safe to merge. For other related pending tickets/PRs, I am collecting them to the daily report for meeting discussion where @spiffxp can decide. |
/hold cancel |
/retest |
Related to #74441.
This is a GCP only change.
This PR:
fluentd-gcp
to collect pod logs to stackdriver withk8s_pod
resource type.@yujuhong @dchen1107 @bmoyles0117