Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optionally use the tool without the operator part #29

Open
aslafy-z opened this issue Feb 24, 2022 · 2 comments
Open

Optionally use the tool without the operator part #29

aslafy-z opened this issue Feb 24, 2022 · 2 comments
Assignees

Comments

@aslafy-z
Copy link
Contributor

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
Copy link
Member

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
Copy link
Collaborator

junotx commented Feb 24, 2022

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants