-
Notifications
You must be signed in to change notification settings - Fork 38.9k
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
[Scheduler] Use allNodes when calculating nextStartNodeIndex #124933
Conversation
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
/cc @alculquicondor |
Please add a release note |
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.
Let's also add an integration test using nodeAffinity, as reported in the issue.
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.
/lgtm
/approve
Thanks @AxeZhan !
LGTM label has been added. Git tree hash: 22c877b53f7130df6d99d567d7fa47cb9e506d3d
|
/retest |
/hold for @alculquicondor to take a final look for integration test. |
…933-upstream-release-1.30 Automated cherry pick of #124933: base on allNodes when calculating nextStartNodeIndex
…933-upstream-release-1.27 Automated cherry pick of #124933: base on allNodes when calculating nextStartNodeIndex
…933-upstream-release-1.29 Automated cherry pick of #124933: base on allNodes when calculating nextStartNodeIndex
…933-upstream-release-1.28 Automated cherry pick of #124933: base on allNodes when calculating nextStartNodeIndex
git clean -xdf go mod download go mod vendor git checkout HEAD -- vendor tar zcvf ../kubernetes_1.30.1.orig.tar.gz --exclude=.git . debuild -uc -us cp kubernetes.spec ../kubernetes_1.30.1-1.spec cp ../kubernetes*1.30.1*.{gz,xz,spec,dsc} /osc/home\:alvistack/kubernetes-kubernetes-1.30.1/ rm -rf ../kubernetes*1.30.1*.* See kubernetes#124933 See kubernetes#124908 Signed-off-by: Wong Hoi Sing Edison <hswong3i@pantarei-design.com>
git clean -xdf go mod download go mod vendor git checkout HEAD -- vendor tar zcvf ../kubernetes_1.28.10.orig.tar.gz --exclude=.git . debuild -uc -us cp kubernetes.spec ../kubernetes_1.28.10-1.spec cp ../kubernetes*1.28.10*.{gz,xz,spec,dsc} /osc/home\:alvistack/kubernetes-kubernetes-1.28.10/ rm -rf ../kubernetes*1.28.10*.* See kubernetes#124933 See kubernetes#124908 Signed-off-by: Wong Hoi Sing Edison <hswong3i@pantarei-design.com>
git clean -xdf go mod download go mod vendor git checkout HEAD -- vendor tar zcvf ../kubernetes_1.29.5.orig.tar.gz --exclude=.git . debuild -uc -us cp kubernetes.spec ../kubernetes_1.29.5-1.spec cp ../kubernetes*1.29.5*.{gz,xz,spec,dsc} /osc/home\:alvistack/kubernetes-kubernetes-1.29.5/ rm -rf ../kubernetes*1.29.5*.* See kubernetes#124933 See kubernetes#124908 Signed-off-by: Wong Hoi Sing Edison <hswong3i@pantarei-design.com>
git clean -xdf go mod download go mod vendor git checkout HEAD -- vendor tar zcvf ../kubernetes_1.28.10.orig.tar.gz --exclude=.git . debuild -uc -us cp kubernetes.spec ../kubernetes_1.28.10-1.spec cp ../kubernetes*1.28.10*.{gz,xz,spec,dsc} /osc/home\:alvistack/kubernetes-kubernetes-1.28.10/ rm -rf ../kubernetes*1.28.10*.* See kubernetes#124933 See kubernetes#124908 Signed-off-by: Wong Hoi Sing Edison <hswong3i@pantarei-design.com>
git clean -xdf go mod download go mod vendor git checkout HEAD -- vendor tar zcvf ../kubernetes_1.29.5.orig.tar.gz --exclude=.git . debuild -uc -us cp kubernetes.spec ../kubernetes_1.29.5-1.spec cp ../kubernetes*1.29.5*.{gz,xz,spec,dsc} /osc/home\:alvistack/kubernetes-kubernetes-1.29.5/ rm -rf ../kubernetes*1.29.5*.* See kubernetes#124933 See kubernetes#124908 Signed-off-by: Wong Hoi Sing Edison <hswong3i@pantarei-design.com>
git clean -xdf go mod download go mod vendor git checkout HEAD -- vendor tar zcvf ../kubernetes_1.30.1.orig.tar.gz --exclude=.git . debuild -uc -us cp kubernetes.spec ../kubernetes_1.30.1-1.spec cp ../kubernetes*1.30.1*.{gz,xz,spec,dsc} /osc/home\:alvistack/kubernetes-kubernetes-1.30.1/ rm -rf ../kubernetes*1.30.1*.* See kubernetes#124933 See kubernetes#124908 Signed-off-by: Wong Hoi Sing Edison <hswong3i@pantarei-design.com>
git clean -xdf go mod download go mod vendor git checkout HEAD -- vendor tar zcvf ../kubernetes_1.28.10.orig.tar.gz --exclude=.git . debuild -uc -us cp kubernetes.spec ../kubernetes_1.28.10-1.spec cp ../kubernetes*1.28.10*.{gz,xz,spec,dsc} /osc/home\:alvistack/kubernetes-kubernetes-1.28.10/ rm -rf ../kubernetes*1.28.10*.* See kubernetes#124933 See kubernetes#124908 Signed-off-by: Wong Hoi Sing Edison <hswong3i@pantarei-design.com>
git clean -xdf go mod download go mod vendor git checkout HEAD -- vendor tar zcvf ../kubernetes_1.29.5.orig.tar.gz --exclude=.git . debuild -uc -us cp kubernetes.spec ../kubernetes_1.29.5-1.spec cp ../kubernetes*1.29.5*.{gz,xz,spec,dsc} /osc/home\:alvistack/kubernetes-kubernetes-1.29.5/ rm -rf ../kubernetes*1.29.5*.* See kubernetes#124933 See kubernetes#124908 Signed-off-by: Wong Hoi Sing Edison <hswong3i@pantarei-design.com>
git clean -xdf go mod download go mod vendor git checkout HEAD -- vendor tar zcvf ../kubernetes_1.30.1.orig.tar.gz --exclude=.git . debuild -uc -us cp kubernetes.spec ../kubernetes_1.30.1-1.spec cp ../kubernetes*1.30.1*.{gz,xz,spec,dsc} /osc/home\:alvistack/kubernetes-kubernetes-1.30.1/ rm -rf ../kubernetes*1.30.1*.* See kubernetes#124933 See kubernetes#124908 Signed-off-by: Wong Hoi Sing Edison <hswong3i@pantarei-design.com>
I am using k3s I am still facing this issue, is it related or different issue? I am facing this issues since k8s 1.29 version. Tried
|
@debugger24 I think this patch should be included in 1.30.2. You can check https://kubernetes.io/releases/patch-releases/#detailed-release-history-for-active-branches for detailed version for each releases. Can you update to 1.30.2 and see if the scheduler will panic? |
It will be included in 1.31. Since I am using k3s looks like I need to wait for k3s team to release 1.31 |
I believe 1.30.2 is enough, maybe let k3s team to do a patch fot this. |
Tried v1.30.2-rc3+k3s1 but didn't work. |
That shouldn't happen. Do you have steps to reproduce? And did you try on other clusters(for example, maybe kind?) |
git clean -xdf go mod download go mod vendor git checkout HEAD -- vendor tar zcvf ../kubernetes_1.28.10.orig.tar.gz --exclude=.git . debuild -uc -us cp kubernetes.spec ../kubernetes_1.28.10-1.spec cp ../kubernetes*1.28.10*.{gz,xz,spec,dsc} /osc/home\:alvistack/kubernetes-kubernetes-1.28.10/ rm -rf ../kubernetes*1.28.10*.* See kubernetes#124933 See kubernetes#124908 Signed-off-by: Wong Hoi Sing Edison <hswong3i@pantarei-design.com>
git clean -xdf go mod download go mod vendor git checkout HEAD -- vendor tar zcvf ../kubernetes_1.29.5.orig.tar.gz --exclude=.git . debuild -uc -us cp kubernetes.spec ../kubernetes_1.29.5-1.spec cp ../kubernetes*1.29.5*.{gz,xz,spec,dsc} /osc/home\:alvistack/kubernetes-kubernetes-1.29.5/ rm -rf ../kubernetes*1.29.5*.* See kubernetes#124933 See kubernetes#124908 Signed-off-by: Wong Hoi Sing Edison <hswong3i@pantarei-design.com>
git clean -xdf go mod download go mod vendor git checkout HEAD -- vendor tar zcvf ../kubernetes_1.30.1.orig.tar.gz --exclude=.git . debuild -uc -us cp kubernetes.spec ../kubernetes_1.30.1-1.spec cp ../kubernetes*1.30.1*.{gz,xz,spec,dsc} /osc/home\:alvistack/kubernetes-kubernetes-1.30.1/ rm -rf ../kubernetes*1.30.1*.* See kubernetes#124933 See kubernetes#124908 Signed-off-by: Wong Hoi Sing Edison <hswong3i@pantarei-design.com>
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #124930
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: