The current implementation of the Storage resource exists primarily as a way to introduce global config for the Aerospike API key manager. In the current implementation, this configuration is consumed at the Portal controller's initialization and not checked again or tied to any controlling logic. In this implementation, we require a controller pod restart to pick up changes to the Storage resource. It would be preferred to have a reconciliation to check the config and update status, as well as notify the Environment resources relying on the API keys auth configs.
The current implementation of the Storage resource exists primarily as a way to introduce global config for the Aerospike API key manager. In the current implementation, this configuration is consumed at the Portal controller's initialization and not checked again or tied to any controlling logic. In this implementation, we require a controller pod restart to pick up changes to the Storage resource. It would be preferred to have a reconciliation to check the config and update status, as well as notify the Environment resources relying on the API keys auth configs.