Concepts

This section walks through what problems Tazuna is trying to solve, and the design choices it makes to address them.

It focuses on why Tazuna is shaped the way it is rather than how to drive it. For concrete command listings and CLI flags, see the Reference; for step-by-step procedures, see the Guides.

How to read this section

The recommended reading order is as follows.

1. Design Philosophy and Intended Use Cases — start here to understand what Tazuna exists for and the environments it is designed for.
2. Overall Architecture — an overview of the components inside the tazuna binary and how they cooperate.
3. Glossary — definitions of the terms used throughout this section.

For more concrete specifications — the tazuna.yaml schema, each manifest backend, and the behavior of state, multi-cluster, and secret integration — see the Reference. If you encounter an unfamiliar term, consult the glossary first.