Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

releng: Re-enable a bootstrap build job for K8s Infra #20712

Merged
merged 1 commit into from
Feb 2, 2021

Conversation

justaugustus
Copy link
Member

This is somewhat of a partial revert of #20663 to re-enable the previous bootstrap-driven K8s Infra build "canary" job with the following adjustments:

  • Job renamed to ci-kubernetes-build-k8s-infra
  • Adjusted limits for K8s Infra (based on previous PR feedback)
  • Fork annotations (so it doesn't get missed when we cut 1.21 RC... though we should have the new jobs ironed out well before that)

Signed-off-by: Stephen Augustus [email protected]

ref: kubernetes/kubernetes#98646, #20663, kubernetes/release#1711, https://kubernetes.slack.com/archives/C09QZ4DQB/p1612269558032700

/assign @hasheddan @saschagrunert
cc: @kubernetes/release-engineering @kubernetes/ci-signal @neolit123
/priority critical-urgent

This is somewhat of a revert to re-enable the previous bootstrap-driven
K8s Infra build "canary" job with the following adjustments:
- Job renamed to `ci-kubernetes-build-k8s-infra`
- Adjusted limits for K8s Infra (based on previous PR feedback)
- Fork annotations (so it doesn't get missed when we cut 1.21 RC)

Signed-off-by: Stephen Augustus <[email protected]>
@k8s-ci-robot k8s-ci-robot added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Feb 2, 2021
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. area/config Issues or PRs related to code in /config area/jobs area/release-eng Issues or PRs related to the Release Engineering subproject sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. labels Feb 2, 2021
Copy link
Contributor

@hasheddan hasheddan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 2, 2021
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hasheddan, justaugustus

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@k8s-ci-robot
Copy link
Contributor

@justaugustus: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

  • key kubernetes-builds.yaml using file config/jobs/kubernetes/sig-release/kubernetes-builds.yaml

In response to this:

This is somewhat of a partial revert of #20663 to re-enable the previous bootstrap-driven K8s Infra build "canary" job with the following adjustments:

  • Job renamed to ci-kubernetes-build-k8s-infra
  • Adjusted limits for K8s Infra (based on previous PR feedback)
  • Fork annotations (so it doesn't get missed when we cut 1.21 RC... though we should have the new jobs ironed out well before that)

Signed-off-by: Stephen Augustus [email protected]

ref: kubernetes/kubernetes#98646, #20663, kubernetes/release#1711, https://kubernetes.slack.com/archives/C09QZ4DQB/p1612269558032700

/assign @hasheddan @saschagrunert
cc: @kubernetes/release-engineering @kubernetes/ci-signal @neolit123
/priority critical-urgent

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/config Issues or PRs related to code in /config area/jobs area/release-eng Issues or PRs related to the Release Engineering subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants