Skip to content

How to install?

Elastic Operator Deployment

1.Please create a namespace of your choice. Example : elastic-logging

kubectl create ns elastic-logging

Note: Please use feeder-service namespace , if required.

2. Clone the git repository

git clone -b dev
- Navigate into the directory that holds eck-operator folder.

3.Helm Install

helm install eck-operator eck-operator/ -n <namespace>
- Navigate into the directory that holds elasticsearch folder.

4.Helm Install

helm install elastisearch elasticsearch/ -n <namespace>
- Navigate into the directory that holds kibana folder.

5.Helm Install

helm install kibana kibana/ -n <namespace>

6. Beats Setup:

  • The agent will be spinned along with Filebeat running along as a sidecar.
  • The filebeat configuration file in the package can be updated to specific Elastic instances, and logs can be viewed in Kibana.

a. Elastic Configuration Parameters:

  • The below Configuration parameters can be updated for elastic configuration.

    (If Default params needs to be modified)

            value: https://<svc-name>
            value: "<svc-port>"
            value: "elastic"
            value: "<elastic-password>"
    To get elastic password
    kubectl get secret elasticsearch-es-elastic-user -o go-template='{{.data.elastic | base64decode}}' -n namespace

b. Command to be Used:

kubectl set env deploy/feeder -n feeder-service ELASTICSEARCH_HOST=”https://elasticsearch-es-http”

c. Update Log Path:

  • To Update the Log path configured, please modify the below log input path under file beat inputs.
            - type: container
            - /log_output/cilium.log

7. Kibana Dashboard

  • Once the filebeat starts listening, an index will be created or updated on the elastic configured and the pushed logs can be seen.
  • In order to create a dashboard, you will need to build visualizations. Kibana has two panels for this
  • One called Visualize and
  • Another called Dashboard
  • In order to create your dashboard, you will first create every individual visualization with the Visualize panel and save them.

8.Successful Installation

kubectl get all -n <namespace>
kubectl port-forward svc/kibana-kb-http 5601:5601
- All the pods should be up and running - Kibana Ui with filebeat index should be seen (after beat installation)

Back to top