Kubernetes Fury Logging

Kubernetes Fury Logging provides a logging stack for the Kubernetes Fury Distribution (KFD).

If you are new to KFD please refer to the official documentation on how to get started with KFD.

Overview

Kubernetes Fury Logging uses a collection of open source tools to provide the most resilient and robust logging stack for the cluster.

The central piece of the stack is the open source search engine opensearch, combined with its analytics and visualization platform opensearch-dashboards. The logs are collected using a node-level data collection and enrichment agent fluentbit, pushing it to the OpenSearch via fluentd. The fluentbit and fluentd stack is managed by Banzai Logging Operator. We are also providing an alternative to OpenSearch: loki.

All the components are deployed in the logging namespace in the cluster.

High level diagram of the stack:

Packages

The following packages are included in the Fury Kubernetes Logging katalog:

Package	Version	Description
cerebro	0.9.4	Web admin tool that helps you manage your Opensearch cluster via a graphical user interface
opensearch-single	2.5.0	Single node opensearch deployment. Not intended for production use.
opensearch-triple	2.5.0	Three node high-availability opensearch deployment
opensearch-dashboards	2.5.0	Analytics and visualization platform for Opensearch
logging-operator	3.17.10	Banzai logging operator, manages fluentbit/fluentd and their configurations
logging-operated	-	fluentd and fluentbit deployment using logging operator
configs	-	Logging pipeline configs to gather various types of logs and send them to OpenSearch
loki-configs	-	Logging pipeline configs to gather various types of logs and send them to Loki
loki-distributed	2.7.3	Distributed Loki deployment
minio-ha	vRELEASE.2023-01-12T02-06-16Z	Three nodes HA MinIO deployment

Click on each package to see its full documentation.

Compatibility

Kubernetes Version	Compatibility	Notes
1.23.x	✅	No known issues
1.24.x	✅	No known issues
1.25.x	✅	No known issues

Check the compatibility matrix for additional informations about previous releases of the modules.

Usage

Prerequisites

Tool	Version	Description
furyctl	>=0.6.0	The recommended tool to download and manage KFD modules and their packages. To learn more about furyctl read the official documentation.
kustomize	>=3.5.0	Packages are customized using kustomize. To learn how to create your customization layer with kustomize, please refer to the repository.

Deployment with OpenSearch

1. List the packages you want to deploy and their version in a Furyfile.yml

bases:
  - name: logging/cerebro
    version: "v3.1.3"
  - name: logging/opensearch-single
    version: "v3.1.3"
  - name: logging/opensearch-dashboards
    version: "v3.1.3"
  - name: logging/logging-operator
    version: "v3.1.3"
  - name: logging/logging-operated
    version: "v3.1.3"
  - name: minio/minio-ha
    version: "v3.1.3"
  - name: logging/configs
    version: "v3.1.3"

See furyctl documentation for additional details about Furyfile.yml format.

2. Execute furyctl vendor -H to download the packages

3. Inspect the download packages under ./vendor/katalog/logging.

4. Define a kustomization.yaml that includes the ./vendor/katalog/logging directory as resource.

resources:
- ./vendor/katalog/logging/cerebro
- ./vendor/katalog/logging/opensearch-single
- ./vendor/katalog/logging/opensearch-dashboards
- ./vendor/katalog/logging/logging-operator
- ./vendor/katalog/logging/logging-operated
- ./vendor/katalog/logging/minio-ha
- ./vendor/katalog/logging/configs
``

5. To deploy the packages to your cluster, execute:

```bash
kustomize build . | kubectl apply -f -

Note: When installing the packages, you need to ensure that the Prometheus operator is also installed. Otherwise, the API server will reject all ServiceMonitor resources.

Deployment with Loki

1. List the packages you want to deploy and their version in a Furyfile.yml

bases:
  - name: logging/loki-distributed
    version: "v3.1.3"
  - name: logging/logging-operator
    version: "v3.1.3"
  - name: logging/logging-operated
    version: "v3.1.3"
  - name: minio/minio-ha
    version: "v3.1.3"
  - name: logging/configs
    version: "v3.1.3"
  - name: logging/loki-configs
    version: "v3.1.3"

See furyctl documentation for additional details about Furyfile.yml format.

2. Execute furyctl vendor -H to download the packages

3. Inspect the download packages under ./vendor/katalog/logging.

4. Define a kustomization.yaml that includes the ./vendor/katalog/logging directory as resource.

resources:
- ./vendor/katalog/logging/loki-distributed
- ./vendor/katalog/logging/logging-operator
- ./vendor/katalog/logging/logging-operated
- ./vendor/katalog/logging/minio-ha
- ./vendor/katalog/logging/loki-configs
``

5. To deploy the packages to your cluster, execute:

```bash
kustomize build . | kubectl apply -f -

Note: When installing the packages, you need to ensure that the Prometheus operator is also installed. Otherwise, the API server will reject all ServiceMonitor resources.

Common Customisations

Setup a high-availability three-node OpenSearch

Logging module offers an out of the box, highly-available setup for opensearch instead of a single node version. To set this up, in the Furyfile and kustomization, you can replace opensearch-single with opensearch-triple.

Configure tolerations and node selectors

If you need to specify tolerations and/or node selectors, you can find some snippets in examples/tolerations and its subfolders.