Simple page to view/display failures-latest.json

[dims]

We have some good data here: http://storage.googleapis.com/k8s-metrics/failures-latest.json

This json file is part of metrics we collect, info here: https://github.com/kubernetes/test-infra/blob/master/metrics/README.md#metrics

We need a simple html page that displays the data as a table similar to something i generated by hand here:

This will help make it easier to go and burndown these long suffering CI jobs that are broken (either fix it or remove it).

Bonus points for

• creating URL(s) to the config definitions in test-infra (example url is https://cs.k8s.io/?q=pull-kubernetes-node-kubelet-serial-cpu-manager&repos=kubernetes/test-infra for the pull-kubernetes-node-kubelet-serial-cpu-manager job)
• creating URL(s) to the prow recent runs (example url is https://prow.k8s.io/?job=pull-kubernetes-node-kubelet-serial-cpu-manager for the same job above)

[k8s-ci-robot]

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

• /sig <group-name>
• /wg <group-name>
• /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

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/test-infra repository.

[CIPHERTron]

/assign

[dims]

Another bonus : Ability to sort the table - https://github.com/kubernetes/kubernetes/issues/118441#issuecomment-1711270183

[CIPHERTron]

Another bonus : Ability to sort the table - kubernetes/kubernetes#118441 (comment)

Sure. That would be easy to implement

The sort functionality will be based on the number of days failed right?

[dims]

Sort by days is fine. we can add Sort by name as well as a stretch goal

[CIPHERTron]

Here's a simple table to display the failures-latest.json [GitHub Repo] https://k8s-metrics-failures-latest.netlify.app

But when I try to fetch it from https://storage.googleapis.com/k8s-metrics/failures-latest.json, I am getting a CORS error. One way to override this is to create a proxy-server 🤔

I'm now working on the bonus features 🙌🏻

[dims]

@CIPHERTron sorry CNCF primarily works with Apache License ... looks like you have marked your repo with a different license.

https://github.com/cncf/foundation/blob/main/allowed-third-party-license-policy.md

[k8s-triage-robot]

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]

The Kubernetes project currently lacks enough active 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 rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[k8s-triage-robot]

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

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/test-infra repository.