CI: Measure TestGrid Flakiness workflow fails due to DNS resolution error for testgrid-data.k8s.io

[AkashKumar7902]

Fixes #21912

What changed

• Switch TestGrid row and header requests from the retired http://testgrid-data.k8s.io host to the official https://testgrid-api.prow.k8s.io API.
• Replace permissions: read-all with the least-privilege permissions the scheduled job needs: contents: read and issues: write.

Why

The scheduled Measure TestGrid Flakiness workflow fails before analysis because testgrid-data.k8s.io no longer resolves. Repairing the endpoint alone is not enough: the periodic commands use --create-issue, while the existing read-only token cannot create the intended flake issues.

Impact

The nightly analysis can fetch results for its four configured TestGrid tabs and create missing type/flake issues. The workflow receives no repository permissions beyond reading contents and managing issues.

Testing

• go test ./... from tools/testgrid-analysis

• make verify-yamllint

• PATH="/opt/homebrew/bin:$PATH" make verify-lint

• Live, non-writing smoke tests for all configured tabs:

  go run . flaky --dashboard=sig-etcd-periodics --tab=ci-etcd-e2e-amd64 --max-days=14 --min-runs=1000000
  go run . flaky --dashboard=sig-etcd-periodics --tab=ci-etcd-unit-test-amd64 --max-days=14 --min-runs=1000000
  go run . flaky --dashboard=sig-etcd-presubmits --tab=pull-etcd-e2e-amd64 --min-runs=1000000
  go run . flaky --dashboard=sig-etcd-presubmits --tab=pull-etcd-unit-test --min-runs=1000000

The live checks deliberately omitted --create-issue, so validation did not write to GitHub.

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: AkashKumar7902
Once this PR has been reviewed and has the lgtm label, please assign spzala for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kubernetes-prow]

Hi @AkashKumar7902. Thanks for your PR.

I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.