Description of problem: Usually, the namespace name for operator downstream should be with 'openshift' as prefix. so the namespace better to use 'openshift-metallb-system' https://github.com/openshift/metallb-operator/blob/main/manifests/4.9/metallb-operator.v4.9.0.clusterserviceversion.yaml#L12 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Please let me know if `openshift-metallb-system` is a default namespace, or if administrators can override and use any namespace. Thanks.
(In reply to Mike McKiernan from comment #1) > Please let me know if `openshift-metallb-system` is a default namespace, or > if administrators can override and use any namespace. Thanks. you can overwrite it to whatever namespace, this is part of CSV is just doc section has no functional impact so in theory this BZ is not a bug
It is not matter of overwriting or overriding at all as the user can/needs to create a namespace for the operator for installing the operator whatever path he chooses - webconsole or manifest files. The user may not prefix the namespace with 'openshift' at all even though it is suggested.
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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759