mirror of https://github.com/k3s-io/k3s
49e7d640d9
Automatic merge from submit-queue Node controller to not force delete pods Fixes https://github.com/kubernetes/kubernetes/issues/35145 - [x] e2e tests to test Petset, RC, Job. - [x] Remove and cover other locations where we force-delete pods within the NodeController. **Release note**: <!-- Steps to write your release note: 1. Use the release-note-* labels to set the release note state (if you have access) 2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. --> ``` release-note Node controller no longer force-deletes pods from the api-server. * For StatefulSet (previously PetSet), this change means creation of replacement pods is blocked until old pods are definitely not running (indicated either by the kubelet returning from partitioned state, or deletion of the Node object, or deletion of the instance in the cloud provider, or force deletion of the pod from the api-server). This has the desirable outcome of "fencing" to prevent "split brain" scenarios. * For all other existing controllers except StatefulSet , this has no effect on the ability of the controller to replace pods because the controllers do not reuse pod names (they use generate-name). * User-written controllers that reuse names of pod objects should evaluate this change. ``` |
||
|---|---|---|
| .. | ||
| BUILD | ||
| cidr_allocator.go | ||
| cidr_allocator_test.go | ||
| cidr_set.go | ||
| cidr_set_test.go | ||
| controller_utils.go | ||
| doc.go | ||
| metrics.go | ||
| nodecontroller.go | ||
| nodecontroller_test.go | ||
| rate_limited_queue.go | ||
| rate_limited_queue_test.go | ||
| test_utils.go | ||