Kubernetes InfluxDB OOMKilled

kubectl-describe-pod-influxdb-monitoring.yaml

Name:   monitoring-influxdb-123456789-ab123
Namespace:  kube-system
Node:   ip-12-34-56-78.ec2.internal/12.34.56.78
Start Time: Thu, 02 Mar 2017 13:07:11 -0700
Labels:   k8s-app=influxdb
    pod-template-hash=123456789
    task=monitoring
Status:   Running

Controllers:  ReplicaSet/monitoring-influxdb-123456789
Containers:
  influxdb:
    Container ID: docker://
    Image:    gcr.io/google_containers/heapster-influxdb-amd64:v1.1.1
    Image ID:   docker://sha256:d3fccbedd1804ec28362bfa27dee04d10d3a2d04f4c6774bc18578f71134f8ab
    Port:
    Limits:
      cpu:  300m
      memory: 2Gi
    Requests:
      cpu:    250m
      memory:   512Mi
    State:    Running
      Started:    Fri, 03 Mar 2017 13:36:09 -0700
    Last State:   Terminated
      Reason:   OOMKilled
      Exit Code:  137
      Started:    Fri, 03 Mar 2017 08:56:20 -0700
      Finished:   Fri, 03 Mar 2017 13:36:08 -0700
    Ready:    True
    Restart Count:  5
    Volume Mounts:
      /data from influxdb-storage (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-12345 (ro)
    Environment Variables:  <none>
Conditions:
  Type    Status
  Ready   True
Volumes:
  influxdb-storage:
    Type: EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
  default-token-12345:
    Type: Secret (a volume populated by a Secret)
    SecretName: default-token-12345
QoS Class:  Burstable
Tolerations:  <none>
No events.