I have several microservices running on Kubernetes. Each microservice is a pod consisting of the microservice container and sidecar container to handle logging. I end up having to define the sidecars for each service, and it is pretty verbose:

apiVersion: v1
kind: ReplicationController
metadata:
  name: thing-doer
spec:
  replicas: 1
  template:
    metadata:
      labels:
        app: thing-doer
    spec:
      containers:
      - name: thing-doer
        image: myregistry/thingdoer
        ports:
        - containerPort: 8080
        volumeMounts:
        - mountPath: /logs
          name: logs
      - name: logger
        image: myregistry/logger
        volumeMounts:
        - mountPath: /logs
          name: logs
        - mountPath: /logger-config
          name: logger-config
      volumes:
      - name: logs
        emptyDir: {}
      - name: logger-config
        configMap:
          name: logger-configmap
          items:
          - key: config-yaml
            path: config.yaml

I end up having to repeat these same steps for each microservice:

1. Create log volume
2. Create log-config volume populated from ConfigMap
3. Create logger container
4. Mount log volume to logger container
5. Mount log volume to microservice container
6. Mount log-config volume to logger container

Is there any to reduce this boilerplate and make it composable somehow? Can I just specify that I want this pod to be "loggable" and have it perform the steps I need?