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

[Proposal] Setup a new SIG for Metering #294

Closed
yunkunrao opened this issue Jan 20, 2021 · 6 comments
Closed

[Proposal] Setup a new SIG for Metering #294

yunkunrao opened this issue Jan 20, 2021 · 6 comments
Labels
kind/proposal Categorizes issue as related to a proposal.

Comments

@yunkunrao
Copy link
Contributor

yunkunrao commented Jan 20, 2021

As metering will be intergrated into KubeSphere as an independent module within toolbox. Metering is based on Prometheus API and provides user with consumption information about the cluster resource. So do we need setup a new SIG for metering or classify it into some other existing SIG?

@yunkunrao
Copy link
Contributor Author

yunkunrao commented Jan 20, 2021

/assign @FeynmanZhou

@FeynmanZhou
Copy link
Member

As metering will be intergrated into KubeSphere as an independent module within toolbox. Metering is based on Prometheus API and provides user with consumption information about the cluster resource. So do we need setup a new SIG for metering or classify it into some other existing SIG?

Let me verify it with TOC.

@FeynmanZhou
Copy link
Member

As I discussed with TOC, @benjaminhuo suggests Metering is supposed to be joined into @kubesphere/sig-observability . How do you think of it?

@LinuxSuRen
Copy link
Member

/kind proposal

@ks-ci-bot ks-ci-bot added the kind/proposal Categorizes issue as related to a proposal. label Feb 7, 2021
@LinuxSuRen
Copy link
Member

Any updates?

@benjaminhuo
Copy link
Member

No need to setup a new sig for metering, it's part of Observability SIG

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/proposal Categorizes issue as related to a proposal.
Projects
None yet
Development

No branches or pull requests

5 participants