-
Notifications
You must be signed in to change notification settings - Fork 827
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
Storage Analysis for Billing #193
Comments
Per bucket? Per path? Costs we think of are:
Figure out bucket structure that makes sense for us from a billing perspective GCR doesn't give us this breakdown, but maybe GCS does Use test data? Simulated load? |
Status quo |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/lifecycle frozen |
Just to document some status here: We are starting to upload some artifacts, so we are starting to see some GCS costs. However these costs are likely going to be much smaller than the transfer costs once we start serving binaries. I added a page to the billing report that just breaks down GCS by project, which actually lines up pretty closely for now and shows that the numbers aren't that big. We might just not need this report. Once we get some data transfer going, then I have a tool to build a report for S3 transfers, so I can probably do something similar for GCS. |
Would be interested in seeing the data. Not super important but may give visibility into what images are high traffic etc. |
We tried turning this on a while back and had to turn it off for reasons I can't recall. May be able to turn it on again soon? |
/assign @hh |
@cncf legal should have an updated @ii Contract soon to included the appropriate PII clauses. I'll pick this up once we have that signed, and can add our team to the appropriate google group + perms. @spiffxp does the appropriate group with perms exist yet or should we work on that as a pair/debug session to ensure principal of least privilege. |
We likely have work to do. #1726 might help in putting together the right role But identifying the right resources to apply it to may take some time. I'm pretty slammed but I'll see if I can find some time next week too follow up with you off PR |
/assign @Riaankl |
I think this is no longer blocked, given that @Riaankl has been doing analysis of images transferred from k8s.gcr.io |
/milestone v1.23 |
Mildly related: #2710 attempts to figure out where images are going Not necessarily how much each is costing us |
/milestone clear |
We need to have more detailed reporting on storage, so we can detail our spend per project.
I'm creating this tracking sub-issue for #156
/cc @justinsb
The text was updated successfully, but these errors were encountered: