1. Quick Start
This walkthrough launches the supplied hello_world.yml playbook against the demo inventory’s localhost host. The host uses a local Ansible connection inside the job’s execution environment, so you do not need a separate SSH target or an SSH private key for this example.
Before you begin:
Install Koios Automation Platform and complete First login. For installation methods, see Install.
Use the initial platform administrator account, or an account with the permissions needed to see the resources and launch the template. This walkthrough uses the administrator.
Before using the release images, obtain registry read access from the project; the installer repository requires a separate read permission. See Registry access for the private-distribution prerequisites.
Ensure the controller can sync the public sample Git repository and the cluster can pull the configured execution environment image and schedule job pods.
1.1. Initial demo data
With the default spec.controller.create_preload_data: true, the controller creates the following data when it has no organizations:
Resource |
Initial content |
|---|---|
Default |
Organization that owns the demo project, inventory and Machine credential. |
Demo Inventory |
Contains |
Demo Credential |
Machine credential containing the initial controller superuser’s username, normally |
Ansible Galaxy |
Managed Galaxy credential pointing to |
Demo Project |
Git project pointing to |
Demo Job Template |
Runs |
Preload data is conditional, not a continuous repair mechanism. It is not created when disabled or when the controller already has an organization. Removing a demo resource does not trigger its recreation while an organization remains. A user without access may also see an incomplete list. If the resources are missing, ask the platform administrator whether this walkthrough applies; use the linked User Guide procedures to create equivalent resources instead of assuming the demo names exist.
The next pages review the resources, sync the project and launch the job. A successful demo verifies this local execution path; it does not establish connectivity to other managed hosts or external services.