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

Fix logrotate.conf for recent podifications #6946

Closed
erictune opened this Issue Apr 17, 2015 · 2 comments

Comments

Projects
None yet
5 participants
@erictune
Copy link
Member

commented Apr 17, 2015

cluster/saltbase/salt/logrotate/init.sls says:
{% set logrotate_files = ['kube-scheduler', 'kube-proxy', 'kubelet', 'kube-apiserver', 'kube-controller-manager'] %}.

However, kube-scheduler, kube-apiserver, and (soon) kube-controller-manager run in pods so they can't be logrotated. So:

  1. remove them from the salt file
  2. consider running logrotate as a sidecar within the pod, and perhaps sending them to the logging storage thing if present.
@ArtfulCoder

This comment has been minimized.

Copy link
Contributor

commented Apr 17, 2015

I will remove this.

The logs from these new pods should be extracted by fluentd just the way users' pods logs get extracted out.

@ArtfulCoder

This comment has been minimized.

Copy link
Contributor

commented May 5, 2015

Currently, kube-scheduler, kube-apiserver, and kube-controller-manager run in pods and still write to log files on the host filesystem using mount.
closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.