Argo Rollout controller looking for cluster scope permissions for Secrets and Configmap for notifications

[kshantaramanUFL]

I have deployed argo-rollouts in argo-rollouts namespace using namespace-install.yaml and used the following args for notifications

 - args:
        - --namespaced
        - --self-service-notification-enabled=true

The secrets and configmap for notifications are both created at the namespace level

k get secret argo-rollouts-notification-secret -n argo-rollouts               
NAME                                TYPE     DATA   AGE
argo-rollouts-notification-secret   Opaque   1      2d3h

k get cm argo-rollouts-notification-configmap -n argo-rollouts
NAME                                   DATA   AGE
argo-rollouts-notification-configmap   19     35m

My controller still complains about lack of cluster role as shown below

 Failed to watch *v1.ConfigMap: failed to list *v1.ConfigMap: configmaps \"argo-rollouts-notification-configmap\" is forbidden: User \"system:serviceaccount:argo-rollouts:argo-rollouts\" cannot list resource \"configmaps\" in API group \"\" at the cluster scope\n" error="<nil>"
time="2023-12-14T00:20:14Z" level=info msg="pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:169: failed to list *v1.Secret: secrets \"argo-rollouts-notification-secret\" is forbidden: User \"system:serviceaccount:argo-rollouts:argo-rollouts\" cannot list resource \"secrets\" in API group \"\" at the cluster scope\n"

My namespace scope role has the required permissions

k get role argo-rollouts -n argo-rollouts -o yaml | grep -C4 configmap | grep -v "apiVersion"
--
- apiGroups:
  - ""
  resources:
  - secrets
  - configmaps
  verbs:
  - get
  - list
  - watch

could some one explain why I am facing this issue and help me fix it? I don't want to give ClusterRole and instead have it use the namespace role. Is it possible to achieve this?

I did check the answer on this and followed the recommendation and that didnt work out!

My rollout controller image is quay.io/argoproj/argo-rollouts:v1.6.3

[kshantaramanUFL]

This has been solved by removing the flag - --self-service-notification-enabled