Collection Requirements
The dependency matrix lists the minimum required component versions for each version of the collection when they became generally available (GA) for both, the control node and managed node.
The minimum required component versions can reach end of life (EOL) before the collection reaches EOL, when this happens, you must update the component to a supported version.
For example, if a collection is released that minimally requires ansible-core version 2.15.0 (Ansible 8.0) and later reaches EOL, a newer supported version of ansible-core must be installed.
Control Node
When you install an Ansible version, review the … (expand for more)
When you install an Ansible (ansible-core) version, review the communities ansible-core support matrix to select the appropriate dependencies. Different releases of ansible-core can require different dependencies such as is the case with Python.
Optionally, you can upgrade the ansible-core version, review the installing Ansible guide and select the appropriate option.
If the control node is Ansible Automation Platform (AAP), review the Red Hat Ansible Automation Platform Life Cycle to select a supported AAP version.
Managed Node
The managed requires the following to be installed … (expand for more)
The managed node requires the following be installed and configured:
Dependency Matrix
The dependency matrix lists the dependencies for both, the control node and managed node … (expand for more)
The dependency matrix lists the dependencies for both, the control node and managed node.
Over time, dependencies will reach EOL, for IBM product lifecycle information, you can search for products using the product’s name, version or ID on the IBM Support product lifecycle page.
Version |
Control Node |
Managed Node |
|---|---|---|
1.6.x |
|
|
1.5.x |
|
|
1.4.x |
|
|
1.3.x |
|
|