| sidebar_position | -6 |
|---|---|
| title | Getting Started |
Start exploring the Apeiro Reference Architecture at different levels of the stack:
- for baremetal with e.g. IronCore's Baremetal Automation
- for existing infrastructure with e.g. Gardener
- for existing Kubernetes clusters with e.g. Platform Mesh or Open Component Model
- for existing workloads with e.g. Open Resource Discovery or Open Component Model
Explore the following Apeiro components for baremetal:
- Baremetal Automation of IronCore - manage physical servers in a Kubernetes-native way.
- IronCore-in-a-Box - evaluate IronCore on a local kind cluster for demo purposes.
Explore the following Apeiro components for existing infrastructure:
- Gardener - provide fully managed Kubernetes service for several infrastructure providers; can also be set up locally.
- Garden Linux - run Kubernetes nodes with a small, auditable Linux image.
Explore the following Apeiro components for existing Kubernetes clusters:
- Platform Mesh as interplay of kcp, OpenMFP, and OpenFGA - provide, discover, and consume services with Kubernetes-native principles.
- Open Component Model - deliver and deploy software across environments with this standard and the corresponding tooling.
- OpenBao - manage and store secrets and public key infrastructure securely.
Explore the following Apeiro components for existing workloads:
- Open Resource Discovery - publish application and service metadata with this open protocol.
- Open Component Model - deliver and deploy software across environments with this standard and the corresponding tooling.
- Assemble Apeiro - the Showroom demonstrates how Apeiro assembles the individual components as a working environment.
- Adapt Apeiro - most components of Apeiro are extensible and adjustable, you can adapt them to your own infrastructure or environment constraints.
- Pick and choose - Apeiro is a toolkit and you can pick-and-choose the components that provide the most value for your use case.