TRT-2741: Add ga-test-status to default loaders

[mstaeble]

Summary

• Adds ga-test-status to the default loader list so it runs as part of the regular fetchdata cronjob
• Placed last in the list since it depends on the prow loader having populated dimension tables (tests, prow_jobs, suites)

Evidence

Production load of all 18 GA releases completed in under 6 minutes when running in-cluster:

Release	BQ fetch	COPY to temp	INSERT...SELECT	Total
4.22 (4.7M rows)	33s	13s	28s	41s
4.21 (3.9M rows)	22s	11s	26s	37s
4.20 (3.0M rows)	18s	8s	20s	28s
4.19 (2.2M rows)	17s	7s	14s	21s
4.18 (1.2M rows)	15s	3s	7s	11s
4.17-4.13	13-15s	1-2s	2-3s	3-5s
Total				~6 min

The loader is idempotent (skips releases already loaded with matching GA date), so on subsequent runs it only processes new GA releases.

Test plan

• go build compiles
• Verified production load timing justifies inclusion in default loaders

🤖 Generated with Claude Code

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

[openshift-ci-robot]

@mstaeble: This pull request references TRT-2741 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

• Adds ga-test-status to the default loader list so it runs as part of the regular fetchdata cronjob
• Placed last in the list since it depends on the prow loader having populated dimension tables (tests, prow_jobs, suites)

Evidence

Production load of all 18 GA releases completed in under 6 minutes when running in-cluster:

Release	BQ fetch	COPY to temp	INSERT...SELECT	Total
4.22 (4.7M rows)	33s	13s	28s	41s
4.21 (3.9M rows)	22s	11s	26s	37s
4.20 (3.0M rows)	18s	8s	20s	28s
4.19 (2.2M rows)	17s	7s	14s	21s
4.18 (1.2M rows)	15s	3s	7s	11s
4.17-4.13	13-15s	1-2s	2-3s	3-5s
Total				~6 min

The loader is idempotent (skips releases already loaded with matching GA date), so on subsequent runs it only processes new GA releases.

Test plan

• go build compiles
• Verified production load timing justifies inclusion in default loaders

@coderabbitai ignore

🤖 Generated with Claude Code

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 openshift-eng/jira-lifecycle-plugin repository.

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@openshift-ci-robot Acknowledged. TRT-2741 needs its target version set to 5.0.0 for this PR's target branch.

[openshift-merge-bot]

Scheduling required tests:
/test e2e

[smg247]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mstaeble, smg247

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [smg247]

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

[openshift-ci]

@mstaeble: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.