forked from rook/rook
Blaine Gardner
3a243d2978
After further consideration and working with the feature for a few weeks, the `configOverride` functionality seems to be more complexity than is worth it for the expected benefit. Users still have the most preferred option of setting configs in Ceph's config database using `ceph cofig set` or the dashboard, and the override ConfigMap still exists for fallback scenarios. The config database can still be used by Rook for setting necessary configs, but the user has no way of telling Rook to do so. Signed-off-by: Blaine Gardner <blaine.gardner@suse.com>