-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
2.5
-
None
-
False
-
-
False
Automation Hub defaults to RWX mode for storage and fails to deploy if that is not available. This was not an issue in 2.4 as AH was optional but now on 2.5 it stays in a failed state and there is various strange behaviors under "Access Management" in the gateway when AH is not responding. There is a workaround of manually editing the AH hub yaml to use RWO mode and it deploys without issue as far as I can tell. Adding an option to have AH use RWO in a way that is not at risk for being overwritten would be ideal.