Skip to content

Updating 1.33 jobs #34668

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

Merged
merged 9 commits into from
Apr 10, 2025
Merged

Updating 1.33 jobs #34668

merged 9 commits into from
Apr 10, 2025

Conversation

jimangel
Copy link
Member

@jimangel jimangel commented Apr 10, 2025

Updated the jobs for the 1.33 rc (kubernetes/sig-release#2755). There's a lively discussion here about some of the issues faced: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1744125003875769

At this point:

  • scripts modified to run on ARM (my machine)
  • config / test_config both manually rotated
  • make file ran to generate configs
  • windows capz jobs were removed from the 1.33.yaml sig-release jobs

/cc @kubernetes/release-managers @mbianchidev

@k8s-ci-robot k8s-ci-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Apr 10, 2025
@k8s-ci-robot k8s-ci-robot requested review from aojea and puerco April 10, 2025 15:48
@k8s-ci-robot k8s-ci-robot added 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 Apr 10, 2025
@jimangel jimangel changed the title [WIP] 1.33 jobs Updating 1.33 jobs Apr 10, 2025
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 10, 2025
@jimangel
Copy link
Member Author

/unhold

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 10, 2025
Copy link
Member

@xmudrii xmudrii left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 10, 2025
@dims
Copy link
Member

dims commented Apr 10, 2025

/lgtm
/approve

Let's iterate :) 🤞🏾

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims, jimangel, xmudrii

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 k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 10, 2025
@k8s-ci-robot k8s-ci-robot merged commit 23e517c into kubernetes:master Apr 10, 2025
7 checks passed
@k8s-ci-robot
Copy link
Contributor

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

  • key generated.yaml using file config/jobs/kubernetes/generated/generated.yaml
  • key 1.29.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.29.yaml
  • key 1.30.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.30.yaml
  • key 1.31.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.31.yaml
  • key 1.32.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.32.yaml
  • key 1.33.yaml using file config/jobs/kubernetes/sig-release/release-branch-jobs/1.33.yaml
  • key dra-1.32.yaml using file ``

In response to this:

Updated the jobs for the 1.33 rc (kubernetes/sig-release#2755). There's a lively discussion here about some of the issues faced: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1744125003875769

At this point:

  • scripts modified to run on ARM (my machine)
  • config / test_config both manually rotated
  • make file ran to generate configs
  • windows capz jobs were removed from the 1.33.yaml sig-release jobs

/cc @kubernetes/release-managers @mbianchidev

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.

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 area/testgrid 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. 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/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants