exoticJetStream eventbus: Skip deployment because of using exotic config

[anamhn]

Hello,
I am using a k8s cluster, in which I would like to have a cluster-wide eventbus, in order not to deploy an eventbus for each project namespace.
I have tried with the default one but didn't achieve that, so I looked into the documentation and start trying to deploy the exotic one.
First I have deployed via helm chart jetstream with the nats and nack helm charts, Then I have created a secret for the exotic eventbus, as specified in the example from the documentation. (https://argoproj.github.io/argo-events/eventbus/jetstream/#exotic)
After the deployment, I discovered that the pods for the eventbus do not start, and I checked by describing the resource:
Name: nats API Version: argoproj.io/v1alpha1 Kind: EventBus Metadata: Finalizers: eventbus-controller Spec: Jetstream Exotic: Access Secret: Key: AAA Name: events URL: nats://nats:4222 Status: Conditions: Status: True Type: Configured Message: Skip deployment because of using exotic config. Reason: Skipped Status: True Type: Deployed Config: Jetstream: Access Secret: Key: AAA Name: events URL: nats://nats:4222
If I try to deploy the eventsource (in the same namespace as the exotic eventbus), in the Message section I get an error regarding the fact that the eventbus is not deployed.
I have also asked on slack, but I am doing something wrong?