This is blocked until the below is supported by the operator
We use the default namespace "kabanero" to list instances of "kabaneros", but eventually the operator will support installing Kabanero instances ("kabaneros") into other namespaces. I couldn't find an issue for it yet, so we need to keep an eye out for this support.
Feature design or visual mockup
Listing all instances will need to get all "kabaneros" in all namespaces and return the namespace associated with the instance.
Then once we know the namespace for each instance we can pass the namespace along with the kabanero instance to all our endpoints that need it, this passeed in namespace will replace the DEFAULT_NAMESPACE variable.
Feature description
This is blocked until the below is supported by the operator
We use the default namespace "kabanero" to list instances of "kabaneros", but eventually the operator will support installing Kabanero instances ("kabaneros") into other namespaces. I couldn't find an issue for it yet, so we need to keep an eye out for this support.
Feature design or visual mockup
Then once we know the namespace for each instance we can pass the namespace along with the kabanero instance to all our endpoints that need it, this passeed in namespace will replace the
DEFAULT_NAMESPACEvariable.Additional context