Skip to content
LogScale Self-Hosted Deployment
This is an archived version of the documentation downloaded from LogScale Documentation Archives. Up to date documentation, and documentation for later versions, is available on LogScale Documentation

### Basic Architecture Configuration

The basic architecture configuration for Kubernetes deployment offers a straightforward approach where all tasks run on all pods, providing cost efficiency and simplicity but limiting individual component scalability. The documentation outlines the advantages and disadvantages of this setup, accompanied by a visual representation of the basic architecture and important notes about network communication across zones for LogScale and Kafka pods.

The basic cluster specification above when deployed would run all tasks on all pods.

Pros:

- Easy to get started, since we only need to specify configurations for one set of cluster pods (aka node pool)

- Cheap, since it may be more efficient if we don't need to run many separate pods to achieve the same amount of work

Cons:

- Can't scale individual logical LogScale components independently

Figure 13. Kubernetes Installation Basic Architecture

### Note

Network communication isn't fully shown. There is communication across zones for LogScale and Kafka pods.

#### Enter search term