This message was deleted.
# general
s
This message was deleted.
d
Can you clarify what you are asking a bit? Do you mean to disable the ability to deploy/run any connectors ever, or just disable any/all running connectors at a given point in time?
a
I think you should be able to achieve what you want by setting
functionsWorkerEnabled=false
in the broker config and not having any function worker nodes configured
d
@David K I was hoping for a method of disabling the ability to deploy connectors entirely on the cluster.
@Alexander Preuß I was hoping you wouldn't say that. We are running the function worker on our cluster with the process runtime. This has worked good for us for conserving resources and still enabling the ability, but we ran into an issue when we were spinning up connectors where it would just continually pull an entire cpu per connector and we are trying to keep our resource utilization rather minimal
d
As far as I know, no such “switch” exists to disable connector deployment. The closest you can come is using Pulsar’s authorization to disable this capability for all users.
d
I see. Thank you