Feature Overview (aka. Goal Summary)

This is a feature required by the AAP self-service (portal) and caters to a broader customer base by aligning with their existing RHEL infrastructure.

The RHDH team will provide a RHEL image mode version of RHDH.

Requirements (aka. Acceptance Criteria):

• A standalone RHEL image mode container is available for deploying RHDH on RHEL 9 VMs.
• RHDH would build the "base image" that Ansible can layer onto when building the portal bootc image.
• It allows the injection of custom files and configurations at build and runtime when creating images (e.g., QCOW images), supporting the RHDH configuration options available in existing RHDH Kubernetes-based deployments.
• Can be installed in an air-gapped environment.
• The RHDH RHEL image supports custom configuration and runtime file injection (e.g., BaseURL, proxy settings), eliminating the need to rebuild the entire image each time.
• The services within the RHDH RHEL appliance (e.g., RHDH, PGSQL pod) can be managed (start, stop, restart, enable, etc) by a Platform Admin. This would allow configuration changes to take effect without deploying a new appliance.
• If an issue or request is related to the RHDH RHEL image, the Ansible support team will forward the support request or issue to the RHDH support team.

Out of Scope (Optional)

• An "Installer" that will deploy and manage RHDH on RHEL. 
• Orchestrator is not available for RHEL-based installations
• Adding additional tools or products to manage high availability is out of scope

Customer Considerations (Optional)

• The Ansible support team will be the first point of contact for self-service portal RHEL installer-related customer support issues or requests.

Documentation Considerations

• Engineering documentation is provided to the Ansible Engineering team, covering system requirements for production loads, installation, and configuration.
• A documented process is provided to the Ansible Engineering team to upgrade the RHDH RHEL image to future versions.