Add example fallback logrotate configuration

Though logs are likely to be managed by log aggregation tooling such as
fluentd, it is still sometimes useful to have additional logration rules
in places as a backup.  This demonstrates that capability.

Change-Id: I62faf85cd1abc04d6be6129d788932814850f4a5

examples/basic/HostSystem.yaml

@@ -12,6 +12,23 @@ data:
       tar_url: https://dl.k8s.io/v1.8.0/kubernetes-node-linux-amd64.tar.gz
       tar_path: kubernetes/node/bin/kubelet
       mode: 0555
+    - path: /etc/logrotate.d/json-logrotate
+      mode: 0444
+      content: |-
+        /var/lib/docker/containers/*/*-json.log
+        {
+            compress
+            copytruncate
+            create 0644 root root
+            daily
+            dateext
+            dateformat -%Y%m%d-%s
+            maxsize 10M
+            missingok
+            notifempty
+            su root root
+            rotate 1
+        }
   images:
     coredns: coredns/coredns:0.9.9
     helm:

examples/complete/HostSystem.yaml

@@ -12,6 +12,23 @@ data:
       tar_url: https://dl.k8s.io/v1.8.0/kubernetes-node-linux-amd64.tar.gz
       tar_path: kubernetes/node/bin/kubelet
       mode: 0555
+    - path: /etc/logrotate.d/json-logrotate
+      mode: 0444
+      content: |-
+        /var/lib/docker/containers/*/*-json.log
+        {
+            compress
+            copytruncate
+            create 0644 root root
+            daily
+            dateext
+            dateformat -%Y%m%d-%s
+            maxsize 10M
+            missingok
+            notifempty
+            su root root
+            rotate 1
+        }
   images:
     coredns: coredns/coredns:0.9.9
     helm: