Hello,

I am wondering if anyone has successfully deployed the helm chart stable/elastic-stack to a DigitalOcean Kubernetes cluster (n.b. the elasticsearch url must be set!).

As far as we can tell, this isn’t possible as resource contention and random errors prevent a successful (and stable) deployment - resulting in a NODE going down; despite attempting to deploy on a cluster with 5 droplets, 10 GB RAM and 10 vCPUs (2 GB RAM per node).

It would be very useful if someone could confirm that they also cannot deploy this chart on DigitalOcean. I am in the process of deploying this chart on GCE and will update this post once that is complete.

Kind regards,

Aaron

p.s. the instructions we have been sent are as follows:

Create tiller service account

kubectl create serviceaccount --namespace kube-system tiller

Create cluster rolebinding for tiller permissions

kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin --serviceaccount=kube-system:tiller

Install and initialize helm

helm init --service-account tiller

update helm repos

helm repo update

Install ELK helm chart

helm install stable/elastic-stack

View services and note the name of the elasticsearch client service.

You will need this in the next steps.

kubectl get services

Edit the elasticsearch url to be equal to:

http://<Your ES client service name>.default.svc.cluster.local:9200

kubectl edit deployment silly-elk-kibana

Edit the logstash statefulset to have the environment variable for ELASTICSEARCH_HOST

equal to the elasticsearch URL we configured in the last step

kubectl edit statefulset silly-elk-logstash

Edit the kibana configmap and set ‘elasticsearch.url’ equal to our elasticsearch url used above.

kubectl edit configmaps silly-elk-kibana

Delete the kibana pod so it spins up with the new configmap.

After a few minutes you should be able to access the kibana service.