-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Remove 1.23 dashboards and job #29230
Conversation
/retest |
b55d615
to
50a59f2
Compare
Other release jobs and testgrid settings should not be touched if the goal is to remove 1.23.. |
@cici37, I think we should update the generated.yaml file since the stable4 should be 1.24 now (instead of 1.23). Otherwise, there is an error at Prow:
And due to this file is auto-generated and should not be edited manually, I execute: make -C releng prepare-release-branch to update it. This command also adds changes to the |
We should be updating the generated file, especially as the input spec changed earlier in this PR and merely running the generator would produce different results. 1.23 should be dropped from all of these jobs. |
@@ -251,30 +251,30 @@ k8sVersions: | |||
- --extract-ci-bucket=k8s-release-dev | |||
version: master | |||
beta: | |||
args: | |||
- --extract=ci/latest-1.28 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmmm I don't think we should have 1.28 yet?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The marker already exists in fact (https://dl.k8s.io/ci/latest-1.28.txt) and points to the latest commit in k/k at the time of writing this comment.
Seems like the auto generated yaml still binds to the wrong version: https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/generated/generated.yaml And also, we should not have 1.28 as Ben mentioned above. I forgot how we use beta before, seems like we were using it for the current released version til the next branch is cut in the past. |
Can we start with a more scoped PR to the other 1.23 jobs aside from the dashboard and the generated jobs? |
The test will not pass if we didn't get generated jobs right with 1.23 removal. I agree we should start with minimized pr to remove 1.23 but I guess the above suggestion is still needed. |
We discussed it on Slack a while ago in some thread and this is wrong. The released version should switch to stable1 as soon as .0 is out, but we were forgetting to do so in the past. That said, proposed changes are correct. I'm wondering why is ramrodo@3940234 reverted? Was that file manually changed so it got reverted? |
A separate question, I tried to run
which gives me different changes than |
@cici37 config-forker is only half of the job, there's also config-rotator that takes care of existing jobs (IIRC). The make command unifies both forker and rotator, so that's the reason why results are different. |
I reverted that commit since the script added the |
@ramrodo Can you try reverting that revert commit? I think that we'll get tests passing, from there we can figure out what to do with 1.28. |
This reverts commit 3940234.
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ramrodo The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@@ -224,7 +224,7 @@ periodics: | |||
cluster: k8s-infra-prow-build | |||
annotations: | |||
testgrid-tab-name: gce-cos-k8sbeta-slow | |||
testgrid-dashboards: sig-release-1.27-informing | |||
testgrid-dashboards: sig-release-1.28-informing | |||
testgrid-num-failures-to-alert: '6' | |||
- tags: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ramrodo Can you try commenting all jobs above this one and then pushing that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm aware this is autogenerated file, but let's give it a try and iterate from there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm wondering if adding the #
characters made this test fail at converting to JSON or it is validating the integrity of the file:
https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/test-infra/29230/pull-test-infra-prow-checkconfig/1651730089395621888
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- --env=ENABLE_CACHE_MUTATION_DETECTOR=true | ||
env: | ||
image: gcr.io/k8s-staging-test-infra/kubekins-e2e:v20230406-23cb1879e3-master | ||
resources: &id001 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ramrodo You need to find the first uncommented reference of id001, then place it with L70-L76.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@xmudrii I'll do it with id002
also
@ramrodo: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
I did a write up on this issue in #29387, please check it and comment there on opinions and next steps. |
Closing in favor of #29387 |
Since v1.23 Kubernetes is out of support now, we should remove the 1.23 dashboards from testgrid and its Job
This PR is the following one of #29172
closes #29242
/sig release
/area release-eng