-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
Don't evict static pods #39059
Don't evict static pods #39059
Conversation
6233042
to
7a28d4b
Compare
Filed #39124 and added a TODO |
@k8s-bot gci gke e2e test this |
Jenkins GCI GKE smoke e2e failed for commit 7a28d4b1a09129d5ca75b29b9df90b387a3e285d. Full PR test history. The magic incantation to run this job again is |
7a28d4b
to
d1850d5
Compare
// --config directory. | ||
// TODO(39124): This is a short term fix, we can't assume static pods | ||
// are always well behaved. | ||
glog.V(4).Infof("eviction manager: NOT evicting static pod %v", pod.Name) |
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.
Is glog level is higher? i think 3 is ok.
// --config directory. | ||
// TODO(39124): This is a short term fix, we can't assume static pods | ||
// are always well behaved. | ||
glog.V(4).Infof("eviction manager: NOT evicting static pod %v", pod.Name) |
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.
Is glog level is higher? i think 3 is ok.
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 think I agree, I want this to show up in production logs
d1850d5
to
18eba97
Compare
Jenkins CRI GCE Node e2e failed for commit 18eba97ce854d50224ed359a67c2cc6dc892a39a. Full PR test history. The magic incantation to run this job again is |
Between #38914 and this pr, I prefer this one to patch both 1.4 and 1.5. We are going to fix the priority inversion issue in a proper way in 1.6. LGTM |
Jenkins Bazel Build failed for commit 18eba97ce854d50224ed359a67c2cc6dc892a39a. Full PR test history. The magic incantation to run this job again is |
@bprashanth bazel build failed, you need to run hack/verify-bazel.sh |
18eba97
to
1743c6b
Compare
Jenkins GCE etcd3 e2e failed for commit 18eba97ce854d50224ed359a67c2cc6dc892a39a. Full PR test history. The magic incantation to run this job again is |
Dawn, re-applied lgtm after rebase |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue |
Commit found in the "release-1.5" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked. |
A follow up to #38914, the desired behavior is to:
I don't think 1 needs a cherrypick if 2 goes in.
partial fix for ##38322