Kubernetes Reference Architecture

This section of the documentation contains Terraform configurations to deploy a Kubernetes / Bare-metal architecture for LogScale.

Important

If you are using an older version of the Reference Architecture, then you can still read the now deprecated material in the following Knowledgebase Article: How-To: Install Kubernetes Reference Architecture.

The logscale-kubernetes terraform modules provide the following architecture choices.

Basic use cases:

  • Development, Testing

  • Smaller Search Teams

  • Minimal ingest processing

Ingress use cases:

  • Ingress tier in specified DMZ

  • Ingress resources not shared with Kubernetes system resources

Dedicated UI use cases:

  • Separated ingress tier

  • Separated UI tier

  • Ingest/Digest on same hosts

Advanced use cases:

  • Dedicated processing tier (ingestion) scaling separate from digest/storage

  • Dedicated UI tier for dashboards and search

  • Segmentation of system responsibilities and independent scaling

Components

All architecture choices rely on the same underlying technologies, as outlined in the following list.

Kubernetes Apps:

  • cert-manager: For automated provisioning of certificates in the environment

  • humio-operator: For provisioning of LogScale clusters in the environment

  • strimzi-operator (optional): For provisioning Kafka broker nodes (kraft mode)

The following guidance box provides links to the main section of this documentation:

Architecture Types

This section describes the supported architecture types.

Requirements

This section describes prerequisites for deploying a Kubernetes reference architecture for LogScale.

Sizing

This section describes suggested sizing for deploying a Kubernetes reference architecture for LogScale.

Build Process

This section describes the build process.

Maintaining

This section describes maintaining, upgrading, and scaling the reference architecture implementation.