Prerequisites

This reference describes what a cluster must provide, and what must already be installed on it, before you apply the first Axual chart. Nothing in this group is an Axual component: those start at Streaming Installation. For the requirements that shape the cluster itself, rather than the software on it, see Infrastructure.

Type

Reference

Goal

Find what to size, install and issue before starting an Axual installation.

Audience

Platform Operators and the infrastructure team who own the target Kubernetes or OpenShift cluster.

When to use

Stage 1 of The installation order, before every other group.

The pages in this section cover the preparation, roughly in the order it is done:

  • Infrastructure Requirements lists what the cluster, network and storage must provide, what you must be able to reach or be granted, and points at the guides for what else is significant enough to have its own.

  • Dependencies explains the operators and services Axual relies on but does not ship, such as Strimzi, cert-manager, the Prometheus stack, a database and Vault, and the integrations a production installation is expected to have in place.

  • Install an Ingress Controller makes services in the cluster reachable from outside it.

  • How to Set Up a Local Loopback Alias gives a local macOS installation the fixed address the platform is reached on.

  • Certificates, TLS and DNS covers the DNS names and certificates the platform needs, the Secret formats the charts read, and how to point a component at them.

  • Preparations creates the namespace, the image pull Secret and installs the Strimzi operator, the last step before the first Axual chart installs.

When the cluster is ready, stage 2 is the choice between the two paths described in Two paths through the installation. If a prerequisite turns out to be missing once the charts run, Troubleshooting covers the symptoms that follow.