Flux installation with Openshift and OLM into a dedicated namespace

Describe the bug

Hello,

I installed Flux v2.3.0 on my lab Openshift 4.14 platform into a dedicated namespace, mpms-fluxcd-operator, using Operator Livecycle Manager (OLM).

apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: fluxcd-operator
  namespace: mpms-fluxcd-operator
spec:
  channel: stable
  installPlanApproval: Manual
  name: flux
  source: community-operators
  sourceNamespace: openshift-marketplace
  startingCSV: flux.v2.3.0

But all the controllers have the default namespace flux-system hard-coded in their deployment args --events-addr=http://notification-controller.flux-system.svc.cluster.local./

      labels:
        app: kustomize-controller
    spec:
      containers:
      - args:
        - --events-addr=http://notification-controller.flux-system.svc.cluster.local./
        - --watch-all-namespaces=true
        - --log-level=info
        - --log-encoding=json
        - --enable-leader-election

You should use the variable RUNTIME_NAMESPACE or replace the url by --events-addr=http://notification-controller/

Steps to reproduce

Create a dedicated namespace, different to flux-system

Create an OperatorGroup to allow user to deploy operator in the namespace with OLM

apiVersion: operators.coreos.com/v1
kind: OperatorGroup
metadata:
name: fluxcd-operator
spec:
targetNamespaces: []

Create a Subscription

apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
name: fluxcd-operator
spec:
channel: stable
installPlanApproval: Manual
name: flux
source: community-operators
sourceNamespace: openshift-marketplace
startingCSV: flux.v2.3.0

Check the deployments

Expected behavior

Args should be : - --events-addr=http://notification-controller.mpms-fluxcd-operator.svc.cluster.local./

Screenshots and recordings

No response

OS / Distro

OpenShift 4.14

Flux version

2.3.0

Flux check

no more details

Git provider

No response

Container Registry provider

No response

Additional context

No response

Code of Conduct

[X] I agree to follow this project's Code of Conduct

fluxcd / flux2