Files
kubernetes/cluster
k8s-merge-robot a3f09700e5 Merge pull request #27409 from adityakali/logrotate.1
Automatic merge from submit-queue

add logrotate service and configuration for GCI

This change mirrors the configuration in cluster/saltbase/salt/logrotate for GCI.

On GCI we use systemd timers (https://www.freedesktop.org/software/systemd/man/systemd.timer.html) and install an hourly timer - kube-logrotate.timer. This will invoke kube-logrotate.service (which calls /usr/sbin/logrotate) once every hour to perform log rotation as per the rotation rules installed under /etc/logrotate.d/.

@kubernetes/goog-image @zmerlynn @dchen1107 @andyzheng0831
2016-06-20 13:40:57 -07:00
..
2016-06-06 14:45:06 +08:00
2016-05-31 10:14:33 -07:00
2016-05-31 10:14:33 -07:00
2016-05-03 10:53:33 -07:00
2016-06-09 15:11:52 -07:00
2016-04-19 13:47:05 +02:00

Cluster Configuration

Deprecation Notice: This directory has entered maintainence mode and will not be accepting new providers. Please submit new automation deployments to kube-deploy. Deployments in this directory will continue to be maintained and supported at their current level of support.

The scripts and data in this directory automate creation and configuration of a Kubernetes cluster, including networking, DNS, nodes, and master components.

See the getting-started guides for examples of how to use the scripts.

cloudprovider/config-default.sh contains a set of tweakable definitions/parameters for the cluster.

The heavy lifting of configuring the VMs is done by SaltStack.

Analytics