-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.14.0
-
None
-
Low
-
No
-
3
-
False
-
Description of problem:
When customers install the CMA in a custom namespace or in the default namespace, a second namespace called "keda" is created. The issue is also described here: https://access.redhat.com/solutions/7046442
Version-Release number of selected component (if applicable):
New installation of CMA in OpenShift Container Platform 4.13
How reproducible:
On customer cluster
Steps to Reproduce:
1. Install the Custom Metrics Autoscaler in a custom namespace
Actual results:
Custom Metrics Autoscaler is installed in the custom namespace, however "keda" namespace is also created
Expected results:
Custom Metrics Autoscaler is installed in the custom namespace, no additional namespace is created
Additional info:
