ci-kubernetes-build-* jobs should build without requiring bootstrap.py scenarios

[justaugustus]

What would you like to be added:

Add machinery to replace the bootstrap.py kubernetes_build.py scenario.

Why is this needed:

• bootstrap.py is deprecated, but still in use for the Kubernetes build jobs
• krel and the underlying libraries are quickly replacing our shell tools. Ideally we should build in CI roughly the same way we do during the release process.

Tracking:

Now

• ([krel] Initial commit krel ci-build command #1698) Create a krel ci-build command which mimics the kubernetes_build.py scenario

• (Cleanup some CI build logic and add k8s-ci-builder image #1700) Create the k8s-ci-builder image to support this use case

• (k8s-ci-builder: Clean up image building configs #1710, releng: Enable image building for k8s-ci-builder test-infra#19909) Enable image building

• (releng: Add a job to test creating CI builds w/o the bootstrap image test-infra#19887, releng: Lower requests/limits for ci-kubernetes-build-no-bootstrap test-infra#19889, releng: Use krte wrapper script to execute no-bootstrap build test-infra#19894) Create a Prowjob (ci-kubernetes-build-no-bootstrap) using the new image and krel ci-build command

• (krel: Properly handle jobs with GCS Suffix set and don't attempt to set ACLs on K8s Infra buckets #1731, pkg/gcp/gcs: Improve GCS path construction/retrieval logic #1738) Don't attempt to set ACLs on K8s Infra buckets

  ref: https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-build-no-bootstrap/1326345795653341184

  FATA Failed to run:: publish release: publish release to GCS: change gs://k8s-release-dev/ci/latest-fast.txt permissions: executing gsutil: command /google-cloud-sdk/bin/gsutil acl ch -R -g all:R gs://k8s-release-dev/ci/latest-fast.txt did not succeed: CommandException: Failed to set acl for gs://k8s-release-dev/ci/latest-fast.txt. Please ensure you have OWNER-role access to this resource.

• (krel: Properly handle jobs with GCS Suffix set and don't attempt to set ACLs on K8s Infra buckets #1731, pkg/gcp/gcs: Improve GCS path construction/retrieval logic #1738) Properly handle jobs with GCS Suffix

  • (pkg/gcp/gcs: Improve GCS path construction/retrieval logic #1738) Version markers write to BuildType path instead of BuildType + GCSSuffix

• (pkg/build: Validate images exist before proceeding with CI builds #1713) Validate images when checking if build exists

• (pkg/gcp/gcs: Improve GCS path construction/retrieval logic #1738) Add basic tests (prioritize version and path handling)

Later

• Cleanup unnecessary flags
• (k8s-ci-builder: Clean up image building configs #1710) Pull krte wrapper script into build job
• (k8s-ci-builder: Clean up image building configs #1710) Set up per-branch build job variants
• Cut over jobs (in order of fastest signal and lowest impact)
  • canary: ci-kubernetes-build-canary: Migrate from bootstrap to krel test-infra#20663
  • canary release branch jobs: releng: Migrate all build canary jobs to krel test-infra#20755
  • master
  • fast
  • release branch jobs
• Deprecate kubernetes_build.py
• Ensure build jobs have RelEng alerts:
  • manual: releng: Update Release Managers' alert emails test-infra#19797
  • presubmit-based:
• Prevent bootstrap images from being used for build jobs

This is related to #1693 and kubernetes/test-infra#19483, but can be completed in parallel.

/assign

[spiffxp]

Where do we stand on the "cut over jobs" part of this, will this happen in v1.21 timeframe?

[justaugustus]

Where do we stand on the "cut over jobs" part of this, will this happen in v1.21 timeframe?

kubernetes/test-infra#20663

[justaugustus]

/milestone v1.21
/priority important-soon

[xmudrii]

cc @saschagrunert to check the status with @justaugustus

[saschagrunert]

@justaugustus can we carve-out the open points and hand it over to a release manager (associate)?

[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

[spiffxp]

Is the checklist above accurate for what remains to be done?

[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

[jeremyrickard]

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

[ameukam]

/reopen

[k8s-ci-robot]

@ameukam: Reopened this issue.

In response to this:

/reopen

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