BUG: KIM controller should be restricted to watch Runtimes only in kcp-system
namespace
#449
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Description
For the moment, the KIM controller is watching Runtime resources in all namespaces in the Kubernetes cluster. To make sure that only the Runtime CR that was created in the designed
kcp-system
namespace is under the control of KIM, we should limit the scope of the controller tokcp-system
only. Or if it is possible we should restrict namespace on Custom Resource level.Linked issues
Bug where KIM tries to reconcile the Runtime CR in
default
namespaceSimilar namespace restriction was implemented in Compass Manager
The text was updated successfully, but these errors were encountered: