Instance types
- Minimum:
m5.2xlarge
- Recommended:
m5.4xlarge
or larger
Storage
ROSA supports the use of both EBS and EFS storage for persistence. In theory, EBS can be employed for theanaconda-storage
volume; but because EBS is
limited to the ReadWriteOnce
access mode, only EFS is acceptable for the
anaconda-persistence
volume. For this reason, we recommend provisioning
a single volume that is large and performant enough to accommodate both
storage requirements, to simplify management.
Please refer to the following pages for information on provisioning an EFS volume:
We recommend the following configuration parameters for this volume:
OwnerUid
: We recommend this be set to the same UID selected to run the Anaconda Enterprise containers.OwnerGid
: We recommend a value of0
, which simplifies access from Kubernetes containers whose primary group is0
by default. If you choose a different GID, it will be necessary to incorporate that into thePersistentVolume
specification.Permissions
:770
or775
. It is important that the directory be group writable.
You can create an EFS access point using the UID/GID defined above.

DNS / SSL
OpenShift imposes a unique subdomain structure to the applications that run on its clusters; for example:Note that even though your ROSA cluster may already be configured to serve SSL, Anaconda Enterprise will still require its own SSL certificate due to the usage of wildcards.
Helm chart customization
OpenShift uses a different DNS server address than the one assumed by default in the helm chart. To ensure that the application uses the proper address, add the following lines, respecting indentation, to yourvalues.yaml
overrides file: