Investigate community-accessible Data Studio reports and data sources

[spiffxp]

The Kubernetes community should be able to create publicly viewable Data Studio reports and data sources that are billed to the kubernetes.io GCP org.

Data Studio ownership / billing is not completely intuitive to me. AFAICT:

• there is some some tie-in with GSuite that allows org admins to restrict sharing outside the org (this is how google.com is setup)
• billing for bigquery usage by a data source can be assigned to a billing project
• access to a report doesn't guarantee access to the data sources used by the report
• creating a report with my gmail.com account allows me to share a report publicly

References:

• share data studio assets with viewers and editors: https://support.google.com/datastudio/answer/7459147?hl=en
• transfer data studio asset to new owner: https://support.google.com/datastudio/answer/9003614
• control access to data: https://support.google.com/datastudio/answer/6371135?hl=en
• connect to bigquery: https://support.google.com/datastudio/answer/6370296?hl=en

My proposal is that we try to set things up such that kubernetes-public is billed for whatever usage is necessary to generate/display reports. WDYT @thockin @cblecker @dims @bartsmykla ?

/assign @thockin
to put on your radar to answer where usage should be billed

/assign @MushuEE @spiffxp
I'm happy to help wield credentials and enable whatever API's are needed, but not sure I can guarantee dedicated time to work on this. @MushuEE has been experimenting with a Data Studio report to replace the dashboards we used to provide via velodrome.k8s.io, but is currently held back by the assets being google.com-only

/wg k8s-infra
/sig testing
/area billing
/area access
/priority important-longterm

[MushuEE]

Much appreciated. I will continue investigation

[spiffxp]

/milestone v1.21

[MushuEE]

For example, you can turn link sharing on to share Data Studio reports with non-Google accounts, include them in emails, blogs or social posts, or embed them in your website.

From HERE

It also looks like you can specify a Project ID for billing within a specific report.

Advanced options
Override Billing Project ID

Specify a different Billing Project ID for this custom query.

HERE

[spiffxp]

/milestone v1.23
/unassign @MushuEE @thockin @spiffxp
All of our bandwidth has been elsewhere. While I'm interested in this, I'm not currently working on it; I'll /assign myself if that ever changes

[spiffxp]

/remove-priority important-longterm
/priority important-soon

[spiffxp]

Trying to create a data studio report as my personal account and see how far that gets me: https://datastudio.google.com/u/1/reporting/fc49b7e4-4622-4244-be3e-91dad5502c9d/page/9IFzB

• bigquery datasource hooked up to k8s-gubernator:build dataset
• uses kubernetes-public as billing project
• I don't think I should be able to use this as a billing project from my personal account...
  • apparently audit.viewer could use anything, opened Auditors should not be able to bill arbitrary projects org-wide #2671
  • apparently I'm also a member of k8s-infra-gcp-accounting, opened groups: update spiffxp membership #2673

[ameukam]

/milestone v1.24

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[ameukam]

/remove-lifecycle stale

[ameukam]

/milestone clear
/lifecycle frozen

[ameukam]

/remove-lifecycle frozen
/milestone v1.26
/priority important-longterm

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[ameukam]

/remove-lifecycle stale
/priority backlog
/lifecycle frozen

[ameukam]

/milestone clear