Elasticsearch plugin on Kubernetes

10/22/2018

I need to restart the Elasticsearch node after installing the injest-attachment plugin on Kubernetes Engine on Google Cloud Platform. I have deployed Elasticsearch on a pod. What is the best way to restart the Elasticsearch nodes?

-- Ben Abey
elasticsearch
kubernetes

2 Answers

10/23/2018

If you have deployed elasticsearch with a replication set, Kubernetes will enforce the number of desired pods automatically so you can simply kill the existing pod and a new one can be created.

kubectl delete pods example-pod-1812877987
-- Dan Bowling
Source: StackOverflow

10/22/2018

If Elasticsearch is running directly on the VM:

systemctl restart elasticsearch

If Elasticsearch is running as a container on docker:

docker restart <container-id>

If Elasticsearch is running as a Kubernetes pod (deployed through a Kubernetes manifest):

  • update the image tag in the manifest if needed, and do kubectl apply
  • Or use kubectl replace or kubectl edit commands

On Kubernetes, ideally, you should use the declarative way of updating the manifests and then do a kubectl apply -f

-- Ijaz Ahmad Khan
Source: StackOverflow