Currently the DaemonSet owns responsibility for both controller and node-driver duties. We should split that up, and deploy the controller duties (both CSI and kube-rs controllers) as a separate Deployment.
listener-operator has done this all the way since stackabletech/listener-operator#1, but we never got around to porting that back to secret-operator.
Currently the DaemonSet owns responsibility for both controller and node-driver duties. We should split that up, and deploy the controller duties (both CSI and kube-rs controllers) as a separate Deployment.
listener-operator has done this all the way since stackabletech/listener-operator#1, but we never got around to porting that back to secret-operator.