ansible-navigator.yml Configuration
ansible-navigator.yml is to navigator what ansible.cfg is to ansible-playbook, and it has the same three-layer precedence: file, environment variable, command line. settings --effective prints the result, which is the only reliable way to answer "where did that value come from".
Bonus: Beyond the Blueprint Guide 44 of 45 Intermediate
- OSUbuntu 26.04 LTS
- ansible-core2.20.1
- Python3.14.4
- TimeAbout 15 min
A key navigator does not recognise is a hard error, not a warning - the run stops and names the unexpected property. ansible.cfg would have ignored it silently, so this is stricter than the tool it wraps.
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| ANS-CTL01 | 192.168.0.36 | Ubuntu 26.04 LTS | Ansible Control Node | 2 Core | 3 GB | 50 GB |
This guide includes
Use this when every navigator run needs the same four flags. This matters because ansible-navigator.yml is to navigator what ansible.cfg is to ansible-playbook - three layers decide which value wins, and a typo stops the run rather than being ignored.
- starting from no configuration file at all
- writing one, where each setting replaces something you were otherwise typing
- confirming which flags it saves you
- working out which of the three layers wins
- making a typo, and finding it caught rather than silently ignored
Before you start
- A control node configured as shown in the first step.
ansible-navigatoronPATHand a container image already pulled.
-
The configuration this guide assumes
-
Start with no file at all
-
Write one
-
The flags it saves
-
Three layers, and which one wins
-
A typo is caught, not ignored