k8s.io icon indicating copy to clipboard operation
k8s.io copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

Deprecate and turn down data studio GCP billing report

Open BenTheElder opened this issue 1 year ago • 2 comments

  1. It doesn't correctly reflect sustained use discounts
  2. We will always have to maintain this versus the built-in billing reports
  3. If we fix https://github.com/kubernetes/k8s.io/issues/4981 we can just grant people access to browse our infra (minus sensitive logs/secrets), billing included
  4. We don't have the equivalent for any other vendor, instead we open their built in billing pages in the SIG call and we have a weekly report from CNCF via ii.coop folks in #sig-k8s-infra slack channel that covers the high level spend for all vendors we have credits with (even SIG K8s Infra TLs don't have access to Azure billing currently)

/sig k8s-infra

BenTheElder avatar Jul 31 '24 20:07 BenTheElder

/priority important-longterm /milestone v1.32

ameukam avatar Aug 06 '24 12:08 ameukam

These reports are wildly over-reporting spend currently by not being commitment aware. We should really take this down.

BenTheElder avatar Sep 23 '24 19:09 BenTheElder

/milestone clear

ameukam avatar Nov 21 '24 09:11 ameukam

cc @xmudrii @mfahlandt (I think we should probably do this as we turn up whatever else we use, or even ahead of it, to avoid confusion about the results, or else we should fix this to include commitments correctly)

BenTheElder avatar Dec 03 '24 23:12 BenTheElder

I'm +1 to turning this down ASAP, it's giving wrong results and we shouldn't use it.

xmudrii avatar Dec 04 '24 11:12 xmudrii

/assign @xmudrii

BenTheElder avatar Dec 04 '24 17:12 BenTheElder

/milestone v1.33

ameukam avatar Dec 18 '24 00:12 ameukam

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Mar 18 '25 01:03 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Mar 18 '25 15:03 xmudrii

/milestone v1.34

ameukam avatar Apr 23 '25 19:04 ameukam

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Jul 22 '25 20:07 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Jul 23 '25 08:07 xmudrii

/lifecycle frozen /milestone clear

ameukam avatar Sep 24 '25 17:09 ameukam