You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 19, 2024. It is now read-only.
For the time default configuration is hardcoded
Make it possible to configure it on Operator level.
The idea is to have the same structure of ConfigMaps/[Secrets] to be deployed with Operator (on operator controller's namespace) to be marshalled on start time, instead of hardcoded strings.
This way Cluster Admin would be able to configure Cluster's defaults.
The text was updated successfully, but these errors were encountered:
For the time default configuration is hardcoded
Make it possible to configure it on Operator level.
The idea is to have the same structure of ConfigMaps/[Secrets] to be deployed with Operator (on operator controller's namespace) to be marshalled on start time, instead of hardcoded strings.
This way Cluster Admin would be able to configure Cluster's defaults.
The text was updated successfully, but these errors were encountered: