Optionally use the tool without the `operator` part

[aslafy-z]

The first controller, named operator, generates configmaps with the ruler and exporter configs and creates deployments for them.
Perhaps this part could be optionally bypassed?

The rules can also be provided to the ruler using some configmaps mounts.

[benjaminhuo]

For now, the ruler watches the rule CRD https://github.com/kubesphere/kube-events/blob/master/config/crs/cluster-rules-default.yaml to load the rule dynamically whenever the rule changes, it not using configmap to store rules.

@junotx Am I correct?

[junotx]

For now, the ruler watches the rule CRD https://github.com/kubesphere/kube-events/blob/master/config/crs/cluster-rules-default.yaml to load the rule dynamically whenever the rule changes, it not using configmap to store rules.

@junotx Am I correct?

Yes, that is right