• What is the nature and description of the request?

This request is to enhance both the documentation and UI support for specifying custom storageClass values across various Ansible Automation Platform (AAP) components when deployed via the Red Hat OpenShift Operator.

While certain storage class parameters (e.g., postgres_storage_class) are technically supported, this functionality is only lightly referenced in the official documentation and not clearly surfaced in the Operator UI. As a result, customers may not be aware that per-component storage class customization is possible.

•  
  Why does the customer need this? (List the business requirements here)

In real-world OpenShift deployments:

1. Organizations often have multiple StorageClasses (e.g., fast, encrypted, nfs, etc.).

1. Compliance, performance, or cost optimization may require AAP components to use different storage backends.

1. Without clear documentation or visible configuration options, misconfigurations or inefficient use of storage resources can occur.

Improving this would:

1. Increase deployment flexibility

1. Reduce support overhead (fewer clarification tickets)

1. Improve automation capabilities, particularly in GitOps and IaC contexts

• How would you like to achieve this? (List the functional requirements here)

Clearly document all supported storage_class fields for:

1. AutomationController

1. AutomationHub

1. EDAController and other AAP components (if applicable)

• List any affected known dependencies: Doc, UI etc..

Documentation: Requires updates to the AAP 2.5+ OpenShift installation and Operator configuration guides

Operator CRDs: Should explicitly expose and define default values for all storage_class fields

• Github Link if any

N/A