Deploy your logging stack

Fury Kubernetes modules are deployed via the furyctl command line tool.

Packages are then customized with kustomize. It lets you create customized Kubernetes resources based on other Kubernetes resource files, leaving the original YAML untouched. To learn how to create you own customization layer with it, please see the kustomize repository.


To deploy the Fury Kubernetes Logging module, you need the following

To deploy elasticsearch-single you will need to allocate the following minimum resources:

  • Resource limits: 2000m for CPU and 3G for memory
  • Storage requirements: 30Gi

To deploy elasticsearch-triple you will need to allocate the following minimum resources:

  • Resource limits for each instance: 2000m for CPU and 3G for memory
  • Storage requirement for each instance: 30Gi
  • Only a single Elasticsearch node can be deployed on each node of the cluster


Module Version / Kubernetes Version 1.14.X 1.15.X 1.16.X 1.17.X 1.18.X
  • Compatible
  • Has issues
  • Incompatible


To start using Fury Kubernetes Logging, you need to use the furyctl and create a Furyfile.yml with the list of all the packages that you want to download.

You can download the packages for a full logging stack including Elasticsaerch, Cerebro, Curator, Fluentd, and Kibana using the following Furyfile.yml :

  - name: logging/cerebro
    version: "v1.5.0"
  - name: logging/curator
    version: "v1.5.0"
  - name: logging/elasticsearch-triple
    version: "v1.5.0"
  - name: logging/fluentd
    version: "v1.5.0"
  - name: logging/kibana
    version: "v1.5.0"

and execute

$ furyctl vendor

to download the packages under ./vendor/katalog/logging.

See furyctl documentation for details about Furyfile.yml format.

To deploy the packages to your cluster, define a kustomization.yaml with the following content:

- ./vendor/katalog/logging/cerebro
- ./vendor/katalog/logging/curator
- ./vendor/katalog/logging/elasticsearch-triple
- ./vendor/katalog/logging/fluentd
- ./vendor/katalog/logging/kibana

Then, execute the following command:

$ kustomize build . | kubectl apply -f -

See kustomize documentation for details about kustomization.yaml format.

Available packages

Common packages:

For a single node Elasticsearch instance, please use:

For a three node HA Elasticsearch cluster, please use:

You can click on each package to see its documentation. For further details please refer to the single package directories in our repository.

Last modified 25.06.2020: FIX: logging requirements (2522eb2)