-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Make fluentd container runtime service configurable. #71124
Make fluentd container runtime service configurable. #71124
Conversation
/lgtm |
/retest |
/lgtm |
/assign @dchen1107 |
/lgtm /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dchen1107, 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 |
@Random-Liu bot requires the cla label, does this command put it back? /check-cla |
blocked by #71242 |
/retest Review the full test history for this PR. Silence the bot with an |
/test pull-kubernetes-e2e-gke |
1 similar comment
/test pull-kubernetes-e2e-gke |
/cc @loburm @mikedanese @loburm we have a couple of PRs failing on pull-kubernetes-e2e-gke consistently today. Can you please help take a look to see if there's a wider GKE issue. this is critical PR blocked on getting into 1.13 release. |
/test pull-kubernetes-e2e-gke |
/retest Review the full test history for this PR. Silence the bot with an |
1 similar comment
/retest Review the full test history for this PR. Silence the bot with an |
/retest |
1 similar comment
/retest |
…1124-upstream-release-1.11 Automated cherry pick of #71124: Make fluentd container runtime service configurable.
…1124-upstream-release-1.12 Automated cherry pick of #71124: Make fluentd container runtime service configurable.
This doesn't change any existing logic.
This fixes a bug on GCE, and only affects GCE.
Previously, we were using the same environment variable
CONTAINER_RUNTIME_NAME
for both fluentd config, and health-monitor.However, this causes an issue on GCE and GKE that when the master is using Docker, and nodes are using other container runtimes (e.g. containerd). There is no way to set master env to configure fluentd to collect containerd logs on nodes, but still run docker health monitor on master, because there is only one
CONTAINER_RUNTIME_NAME
environment variable.This is a critical urgent issue fix for Kubernetes on GCE.