Ansible Automation Platform EDA Controller
Description
Ansible Automation Platform is an enterprise automation platform for the entire IT organization, no matter where you are in your automation journey.
The automation controller provides a user interface and REST API to manage, schedule, launch, track, and audit automation.
Ansible Event-Driven Ansible Controller is a standardized way to configure and run ansible-rulebooks to trigger automation.
Products using this container
General information
The following information was extracted from the containerfile and other sources.
| Summary | Red Hat Event-Driven Ansible Controller is a fully-featured console and REST API for event driven automation. |
| Description | Red Hat Event-Driven Ansible Controller helps you scale IT automation, manage complex deployments and speed productivity. |
| Provider | Red Hat |
| Maintainer | Ansible Automation Platform Productization Team |
Technical information
The following information was extracted from the containerfile and other sources.
| Repository name | ansible-automation-platform-25/eda-controller-rhel8 |
| Image version | 1.1.13 |
| Architecture | amd64 |
| Exposed ports | [] |
| User | eda |
| Working directory | /var/lib/ansible-automation-platform/eda |
Use the following instructions to get images from a Red Hat container registry using registry service account tokens. You will need to create a registry service account to use prior to completing any of the following tasks.
Using OpenShift secrets
First, you will need to add a reference to the appropriate secret and repository to your Kubernetes pod configuration via an imagePullSecrets field.
Then, use the following from the command line or from the OpenShift Dashboard GUI interface.
Using podman login
Use the following command(s) from a system with podman installed
Using docker login
Use the following command(s) from a system with docker service installed and running
Use the following instructions to get images from a Red Hat container registry using your Red Hat login.
Using OpenShift
For best practices, it is recommended to use registry tokens when pulling content for OpenShift deployments.
Using podman login
Use the following command(s) from a system with podman installed
Using docker login
Use the following command(s) from a system with docker service installed and running
Getting source containers
Source code is available for all Red Hat UBI-based images in the form of downloadable containers. Here are a few things you should know about Red Hat source containers.
- Although they are packaged as containers, source containers cannot be run. So instead of using podman pull to get them to your system, use the skopeo command.
- Source containers are named based on the binary containers they represent. So, for example, to get the source container for a particular standard RHEL UBI 8 container (registry.access.redhat.com/ubi8/ubi8.1-397) you simply append -source to get the source code container for that image (registry.access.redhat.com/ubi8/ubi8.1-397-source).
- The skopeo command is recommended for getting source containers. With skopeo, you copy a source container to a directory on your local system for you to examine.
- Once a source container is copied to a local directory, you can use a combination of tar,gzip, and rpm commands to work with that content.
Step one
Use skopeo to copy the source image to a local directory
Step two
Inspect the image
Step three
Untar the contents
Step four
Begin examining and using the content.
