<p>I have spun up a Kubernetes cluster in AWS using the official "kube-up" mechanism.  By default, an addon that monitors the cluster and logs to InfluxDB is created.  It has been <a href="https://stackoverflow.com/questions/33068639/kubernetes-pods-some-die-after-running-for-a-day">noted in this post</a> that InfluxDB quickly fills up disk space on nodes, and I am seeing this same issue.</p>

<p>The problem is, when I try to kill the InfluxDB replication controller and service, it "magically" comes back after a time.  I do this:</p>

<pre><code>kubectl delete rc --namespace=kube-system monitoring-influx-grafana-v1
kubectl delete service --namespace=kube-system monitoring-influxdb
kubectl delete service --namespace=kube-system monitoring-grafana
</code></pre>

<p>Then if I say:</p>

<pre><code>kubectl get pods --namespace=kube-system
</code></pre>

<p>I do not see the pods running anymore.  However after some amount of time (minutes to hours), the replication controllers, services, and pods are back.  I don't know what is restarting them.  I would like to kill them permanently.</p>

<p>You probably need to remove the manifest files for influxdb from the <code>/etc/kubernetes/addons/</code> directory on your "master" host. Many of the <code>kube-up.sh</code> implementations use a service (usually at <code>/etc/kubernetes/kube-master-addons.sh</code>) that runs periodically and makes sure that all the manifests in <code>/etc/kubernetes/addons/</code> are active.</p>

<p>You can also restart your cluster, but run <code>export ENABLE_CLUSTER_MONITORING=none</code> before running <code>kube-up.sh</code>. You can see other environment settings that impact the cluster <code>kube-up.sh</code> builds at <code>cluster/aws/config-default.sh</code></p>
