Create Looker Studio Analytics Dashboard for k8s.dev

[TineoC]

Description

The main Kubernetes website (kubernetes.io) has a public analytics dashboard built with Looker Studio (link). Currently, the Kubernetes contributor site (k8s.dev) does not have a similar dashboard, making it difficult for the community to track usage and engagement.

Investigation has shown that Google Analytics is already enabled in production for k8s.dev. However, the real Google Analytics ID is managed as a Netlify environment variable and is not visible in the source code (which uses a placeholder UA-00000000-0).

Proposed Action

1. Investigate Netlify Access: Identify who has administrative access to the k8s.dev Netlify project. Potential candidates based on project history include mrbobbytables, Tim Bannister, or the SIG Contributor Experience leads.
2. Retrieve Production GA ID: Once access is established, retrieve the production Google Analytics ID from the Netlify dashboard.
3. Create Dashboard: Use the production ID to create a Looker Studio dashboard similar to the one for kubernetes.io.
4. Community Access: Follow the standard community process to provide access or visibility to the SIG ContribEx leads and the broader community.

@kubernetes/sig-contributor-experience-leads
@kubernetes/sig-contributor-experience

/kind feature
/sig contributor-experience

[k8s-ci-robot]

@TineoC: The label(s) area/infrastructure cannot be applied, because the repository doesn't have them.

Details

In response to this:

Description

The main Kubernetes website (kubernetes.io) has a public analytics dashboard built with Looker Studio (link). Currently, the Kubernetes contributor site (k8s.dev) does not have a similar dashboard, making it difficult for the community to track usage and engagement.

Investigation has shown that Google Analytics is already enabled in production for k8s.dev. However, the real Google Analytics ID is managed as a Netlify environment variable and is not visible in the source code (which uses a placeholder UA-00000000-0).

Proposed Action

1. Investigate Netlify Access: Identify who has administrative access to the k8s.dev Netlify project. Potential candidates based on project history include Bob Killen, Tim Pepper, or the SIG Contributor Experience leads.
2. Retrieve Production GA ID: Once access is established, retrieve the production Google Analytics ID from the Netlify dashboard.
3. Create Dashboard: Use the production ID to create a Looker Studio dashboard similar to the one for kubernetes.io.
4. Community Access: Follow the standard community process to provide access or visibility to the SIG ContribEx leads and the broader community.

Context

The following community discussion highlights the need and the current blockers:

• chris-short: "Yup. We don't have that for K8s.dev sadly"
• Christopher Tineo: "Google Analytics is actually enabled in production. The things is that only admins have access to Netlify to see the config"
• kaslin: "Hm who would be admins for k8s.dev? Bob did a lot on it at one point. Josh surely knows more old lore on it than us"
• chris-short: "It's a variable in Netlify"

Requirements

• A Google account for the dashboard creator.
• Approval from SIG ContribEx leads.
• Coordination with SIG K8s Infra if necessary.

/kind feature
/area infrastructure
/sig contributor-experience

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[TineoC]

@jberkus do you have access to the netlify admin dashboard for this project?

[kaslin]

I was thinking @lmktfy, Not Tim Pepper. Tim, do you know anything about the Netlify or analytics dashboard for k8s.dev?

[jberkus]

I do not have access.