Migrate jobs away from deprecated bootstrap usage

[spiffxp]

This is an umbrella issue to track migrating job configs away from bootstrap and instead use pod-utils.

Bootstrap has been deprecated for a few years at this point, and jobs that use bootstrap.py have been unsupported by test-infra-oncall for at least 1.5 years (ref: #14392). Pod-utils are the documented and supported way of writing prowjobs: https://github.com/kubernetes/test-infra/tree/master/config/jobs#job-cookbook

One way to be helpful: PR in a guide on how to do this! Relevant content to source from:

• @dims put together a guide https://gist.github.com/dims/c1296f8ed42238baea0a5fcae45f4cf4
• @rikatz went through this for pull-kubernetes-node-e2e
  • Create a node e2e testjob with Podutils to validate migration #19942
  • Update e2e node test job to be optional and use the right scenario #19947
  • New attempt to make e2e nodes work without bootstrap.py #19948
  • Correct the node e2e test image config location #19949
  • Fix pull-kubernetes-node-e2e-podutil #19951

Another way to help: produce a tool, script or dashboard that keeps track of what has and has not been migrated. We could either link to its results from this issue, or periodically update this issue with the results.

The most concrete way to help: migrate the jobs you or your SIG owns

/lifecycle frozen
/priority important-longterm
/sig testing
Once we have tracking of which sigs own jobs that use bootstrap, we can tag with appropriate sigs.
/area jobs
/area bootstrap
/area prow/pod-utils
/help

[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:

This is an umbrella issue to track migrating job configs away from bootstrap and instead use pod-utils.

Bootstrap has been deprecated for a few years at this point, and jobs that use bootstrap.py have been unsupported by test-infra-oncall for at least 1.5 years (ref: #14392). Pod-utils are the documented and supported way of writing prowjobs: https://github.com/kubernetes/test-infra/tree/master/config/jobs#job-cookbook

One way to be helpful: PR in a guide on how to do this! Relevant content to source from:

• @dims put together a guide https://gist.github.com/dims/c1296f8ed42238baea0a5fcae45f4cf4
• @rikatz went through this for pull-kubernetes-node-e2e
• Create a node e2e testjob with Podutils to validate migration #19942
• Update e2e node test job to be optional and use the right scenario #19947
• New attempt to make e2e nodes work without bootstrap.py #19948
• Correct the node e2e test image config location #19949
• Fix pull-kubernetes-node-e2e-podutil #19951

Another way to help: produce a tool, script or dashboard that keeps track of what has and has not been migrated. We could either link to its results from this issue, or periodically update this issue with the results.

The most concrete way to help: migrate the jobs you or your SIG owns

/lifecycle frozen
/priority important-longterm
/sig testing
Once we have tracking of which sigs own jobs that use bootstrap, we can tag with appropriate sigs.
/area jobs
/area bootstrap
/area prow/pod-utils
/help

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.

[k8s-ci-robot]

@spiffxp: The label(s) area/prow/pod-utils cannot be applied, because the repository doesn't have them

In response to this:

This is an umbrella issue to track migrating job configs away from bootstrap and instead use pod-utils.

Bootstrap has been deprecated for a few years at this point, and jobs that use bootstrap.py have been unsupported by test-infra-oncall for at least 1.5 years (ref: #14392). Pod-utils are the documented and supported way of writing prowjobs: https://github.com/kubernetes/test-infra/tree/master/config/jobs#job-cookbook

One way to be helpful: PR in a guide on how to do this! Relevant content to source from:

• @dims put together a guide https://gist.github.com/dims/c1296f8ed42238baea0a5fcae45f4cf4
• @rikatz went through this for pull-kubernetes-node-e2e
• Create a node e2e testjob with Podutils to validate migration #19942
• Update e2e node test job to be optional and use the right scenario #19947
• New attempt to make e2e nodes work without bootstrap.py #19948
• Correct the node e2e test image config location #19949
• Fix pull-kubernetes-node-e2e-podutil #19951

Another way to help: produce a tool, script or dashboard that keeps track of what has and has not been migrated. We could either link to its results from this issue, or periodically update this issue with the results.

The most concrete way to help: migrate the jobs you or your SIG owns

/lifecycle frozen
/priority important-longterm
/sig testing
Once we have tracking of which sigs own jobs that use bootstrap, we can tag with appropriate sigs.
/area jobs
/area bootstrap
/area prow/pod-utils
/help

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.

[spiffxp]

As an FYI, jobs that migrate away from bootstrap will lack an Infra-Commit column in testgrid: #20650. This is not a blocker to migration, and is probably a good thing (one less thing to bisect).

I strongly suspect kubernetes/test-infra code being checked out in a job's container isn't actually necessary for the vast majority of jobs that make the switch away from bootstrap.

[spiffxp]

Things to help track our status:

• Add tests to log jobs using deprecated bootstrap, scenarios #20825 added tests to log jobs that are deprecated
• jobs: add summary lines to jobs tests #22838 added summary lines to a number of tests

[spiffxp]

/kind cleanup

[dims]

xref: #30846

[dims]

@spiffxp will be proud of us :) #30846

/close

[k8s-ci-robot]

@dims: Closing this issue.

In response to this:

@spiffxp will be proud of us :) #30846

/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.