Install with Ansible
Before running these steps, obtain project-granted read access to the private koios-installer
repository and the images in ghcr.io/koiosplatform. These are separate permissions; see
Access prerequisites. Run installer commands from an authorized checkout
of the release tag described in Install.
To request access, write to the Koios project at asield03@gmail.com.
The installer includes the collection koios.installer (named koios.platform until 2026.11.11). Its role install applies the same manifests
of the release (OLM or Kustomize), creates the pull Secrets from an auth file without printing it,
waits for the operators and creates the platform, waiting until it is Successful.
Requirements
On the machine that runs Ansible: ansible-core 2.16 or later, the kubernetes.core collection and
the kubernetes Python library, and a kubeconfig whose current context points to the cluster. On
OpenShift, ghcr.io must be in the global pull secret (Registry access).
Use
ansible-galaxy collection install ./ansible
ansible-playbook koios.installer.install -e koios_registry_authfile=$PWD/ghcr-auth.json
The role detects OpenShift: there it installs with OLM, elsewhere with Kustomize. Variables:
Variable |
Default |
Meaning |
|---|---|---|
|
|
Install mode |
|
|
|
|
|
Platform namespace |
|
(required) |
Registry auth file; only its |
|
|
Create the |
|
|
Its name |
|
|
Its spec (Configure) |
|
|
Seconds to wait for the operators and the platform |
Example with automation hub on a single-node volume:
ansible-playbook koios.installer.install -e koios_registry_authfile=$PWD/ghcr-auth.json \
-e '{"koios_platform_spec": {"hub": {"file_storage_access_mode": "ReadWriteOnce"}}}'
Running it again is safe: nothing changes if the cluster already matches. The role refuses to change the install mode or the OLM scope of an existing install (uninstall the operators first).