When you install the operator Helm chart, you can set
true in your
values.yaml file to direct the operator to send the contents of the operator’s logs to Elasticsearch.
Typically, you would have already configured Elasticsearch and Kibana in the
Kubernetes cluster, and also would have specified
elasticSearchPort in your
values.yaml file to point to where Elasticsearch is already running.
This sample configures the Elasticsearch and Kibana deployments and services. It’s useful for trying out the operator in a Kubernetes cluster that doesn’t already have them configured.
It runs the Elastic Stack on the same host and port that the operator’s Helm chart defaults
to, therefore, you only need to set
true in your
To control Elasticsearch memory parameters (Heap allocation and Enabling/Disabling swapping), open the file
elasticsearch_and_kibana.yaml, search for
env variables of the Elasticsearch container and change the values of the following:
ES_JAVA_OPTS: value may contain, for example,
-Xmx512mto lower the default memory usage (please be aware that this value is applicable for demonstration purposes only and it is not the one recommended by Elasticsearch).
bootstrap.memory_lock: value may contain
true(enables the usage of
mlockall, to try to lock the process address space into RAM, preventing any Elasticsearch memory from being swapped out) or
false(disables the usage of
To install Elasticsearch and Kibana, use:
$ kubectl apply -f kubernetes/samples/scripts/elasticsearch-and-kibana/elasticsearch_and_kibana.yaml
To remove them, use:
$ kubectl delete -f kubernetes/samples/scripts/elasticsearch-and-kibana/elasticsearch_and_kibana.yaml