Choose a plug-in delivery method
Ansible plug-ins for Red Hat Developer Hub support two delivery methods. Choose the method that fits your environment.
Ansible automation portal supports two plug-in delivery methods:
- OCI container delivery (recommended): Ansible automation portal automatically pulls an Open Container Initiative (OCI) container from
registry.redhat.iothat contains the plug-ins. Use this method for new installations. - HTTP plug-in registry (deprecated): Manually create an HTTP plug-in registry that hosts plug-in tarball files. This method is deprecated and will be removed in a future release of Ansible Automation Platform. Existing installations that use this method should migrate to OCI container delivery.
If you are installing Ansible automation portal in a disconnected or air-gapped OpenShift Container Platform environment, complete the pre-installation configuration in this chapter and then follow the procedures in the disconnected installation chapter. The disconnected installation chapter includes additional steps for mirroring container images, configuring registry authentication, and installing the Helm chart in isolated environments.
- OCI container delivery
Use OCI container delivery to pull plug-in artifacts fromregistry.redhat.io/ansible-automation-platform/automation-portal. The plug-in version must match theimageTagInfovalue in your Helm chart configuration. This is the recommended method for new installations. - Choose a plug-in delivery method
Ansible automation portal supports two plug-in delivery methods. Choose OCI container delivery for new installations, or plan to migrate from the deprecated HTTP plug-in registry. - Determine version tags before you install
Record the version values that you need before you install the Helm chart or mirror images for Ansible automation portal.