Make it clear which version of kubetest or kubetest2 is being used

[spiffxp]

We may have deprecated kubetest, but it's still in use. Whatever we do here should support kubetest2 or be included in kubetest2

kubernetes/kubernetes#96987 (comment) is an example of confusion over the fact that changes to kubetest don't take effect until job configs are updated to a new image (e.g. kubekins)

We could stand to document how changes flow a better. But it might help for troubleshooting if we make it clearer what version of kubetest is being used.

Ideas include:

• log the version kubetest was built at
• have kubetest log its version
• store version info as an artifact
• include kubetest's version in metadata.json so it can be displayed as a custom testgrid column (maybe related to Infra-Commit testgrid column missing for pod-utils jobs #20650)

[spiffxp]

/help
/kind cleanup
/sig testing
/area kubetest
/priority important-soon
/milestone v1.21

[BenTheElder]

cc @amwat

[supriya-premkumar]

/assign

[spiffxp]

/remove-help
Please ping with any questions if you need help

[amwat]

Whatever we do here should support kubetest2 or be included in kubetest2

tracked here: kubernetes-sigs/kubetest2#108

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[spiffxp]

/help
/remove-lifecycle stale

[k8s-ci-robot]

@spiffxp:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help
/remove-lifecycle stale

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.

[supriya-premkumar]

Hi @spiffxp, apologies for the delay. I have this WIP PR
I will revive the PR and work on this one. Thank you 🙏🏽

[spiffxp]

/milestone v1.23
What remains to be done here? I swear I talked about this last meeting and have already forgotten the things we linked through to discover that there was still work to actually add it to metadata.json and setup testgrid column headers

[amwat]

We still need to add a testgrid column-header in https://github.com/kubernetes/test-infra/blob/master/config/testgrids/default.yaml#L10

to read https://github.com/kubernetes/test-infra/pull/21276/files#diff-71dd7bf85cfecc6c2c2fa0956ad5f182433bcc0f287aaa83f2052eb3f8ba9710R525

(probably we should consider an agnostic name to also cover kubetest2)

I also have a PR open to square off the kubetest2 parts kubernetes-sigs/kubetest2#162

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 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 rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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:

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

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

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active 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:

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

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

/close

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.