Description of problem: In Heketi v4, the DB is also stored in Kube Secret. It may cause issues especially in CNS or scaled setups. We need to revisit this DB migration introduced in Heketi v4 release. Version-Release number of selected component (if applicable): heketi-v4 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
--snip-- Individual secrets are limited to 1MB in size. This is to discourage creation of very large secrets which would exhaust apiserver and kubelet memory. However, creation of many smaller secrets could also exhaust memory. More comprehensive limits on memory usage due to secrets is a planned feature. --/snip--
Upstream issue # https://github.com/heketi/heketi/issues/697
This issue is fixed by https://github.com/heketi/heketi/pull/713
The revert of secret need changes in heketi and also in cns-deploy script. This bug will track the changes in heketi. I will open a new bug for cns-deploy.
Verified
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:1111