Elastic Search & Kibana

install elastic search and kibana using helm for server logs to install elasticsearch, add the elastic repository in helm helm repo add elastic https //helm elastic co now, use the curl command to download the values yaml file containing configuration information curl o https //raw\ githubusercontent com/elastic/helm charts/master/elasticsearch/examples/minikube/values yaml use the helm install command and the values yaml file to install the elasticsearch helm chart helm install elasticsearch elastic/elasticsearch f /values yaml the f option allows specifying the yaml file with the template if you wish to install elasticsearch in a specific namespace, add the n option followed by the name of the namespace helm install elasticsearch elastic/elasticsearch n \[namespace] f /values yaml now check if the cluster members are up kubectl get pods namespace=default l app=elasticsearch master w the other option is to use the helm test command to examine the cluster’s health helm test elasticsearch to install kibana on top of elasticsearch helm install kibana elastic/kibana check if all the pods are ready kubectl get pods after you set up port forwarding, access elasticsearch, and the kibana gui by typing https //localhost 5601 in your browser in order to connect logger with elasticsearch, update config file(values yml) for xr env api extraenv elastic host for e g https //\<username> \<password>@\<host> \<port> upgrading an existing helm deployment one of the features of helm is being able to easily upgrade deployments with new values the command to do this is very similar to the install command helm upgrade reuse values f \</path/to/ values yaml> set api image tag=\<latest github commit sha>,client image tag=\<latest github commit sha>,instanceserver image tag=\<latest github commit sha> \<release name> ir engine/ir engine \ reuse values says to carry over all configuration values from the previous deployment this is most important for tags, since they're usually set inline with the helm install/upgrade command, not a helm config using f \<config file> and set \<variables> after it will apply any changes on top of the carryover values if you're not deploying a new build of the codebase, you can skip the entirety of the set image tag=\<sha>