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

Storage Analysis for Billing #193

Open
hh opened this issue Feb 20, 2019 · 16 comments
Open

Storage Analysis for Billing #193

hh opened this issue Feb 20, 2019 · 16 comments
Assignees
Labels
area/billing Issues or PRs related to billing lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra.

Comments

@hh
Copy link
Member

hh commented Feb 20, 2019

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

@spiffxp spiffxp added this to the ready-to-migrate milestone Apr 30, 2019
@spiffxp spiffxp added the area/billing Issues or PRs related to billing label May 1, 2019
@spiffxp
Copy link
Member

spiffxp commented May 1, 2019

Per bucket? Per path?

Costs we think of are:

  • storage at rest
  • bandwidth delivered (likely the larger of the two)

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?

@spiffxp
Copy link
Member

spiffxp commented May 1, 2019

/assign @justinsb @thockin

@spiffxp
Copy link
Member

spiffxp commented Jun 26, 2019

Status quo

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 24, 2019
@thockin
Copy link
Member

thockin commented Sep 26, 2019

/lifecycle frozen
/remove-lifecycle stale
/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 26, 2019
@justinsb
Copy link
Member

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.

@spiffxp
Copy link
Member

spiffxp commented Oct 28, 2020

Would be interested in seeing the data. Not super important but may give visibility into what images are high traffic etc.

@spiffxp spiffxp removed this from the ready-to-migrate milestone Jan 13, 2021
@spiffxp
Copy link
Member

spiffxp commented Jan 20, 2021

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?

@spiffxp spiffxp added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Jan 22, 2021
@spiffxp
Copy link
Member

spiffxp commented Jan 22, 2021

/assign @hh
since you had expressed interest in working on this

@hh
Copy link
Member Author

hh commented Feb 24, 2021

@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.

@spiffxp
Copy link
Member

spiffxp commented Feb 26, 2021

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

@riaankleinhans
Copy link
Contributor

/assign @Riaankl

@spiffxp
Copy link
Member

spiffxp commented Jul 9, 2021

I think this is no longer blocked, given that @Riaankl has been doing analysis of images transferred from k8s.gcr.io

@spiffxp spiffxp added this to the v1.22 milestone Jul 9, 2021
@spiffxp
Copy link
Member

spiffxp commented Aug 4, 2021

/milestone v1.23

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.22, v1.23 Aug 4, 2021
@spiffxp
Copy link
Member

spiffxp commented Sep 29, 2021

Mildly related: #2710 attempts to figure out where images are going

Not necessarily how much each is costing us

@k8s-ci-robot k8s-ci-robot added sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. and removed wg/k8s-infra labels Sep 29, 2021
@ameukam
Copy link
Member

ameukam commented Dec 14, 2021

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.23 milestone Dec 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/billing Issues or PRs related to billing lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra.
Projects
Status: Reporting, Audit & Logging
Development

No branches or pull requests

8 participants