mirror of https://github.com/k3s-io/k3s
2c50d2b6fc
Automatic merge from submit-queue Update how we detect overlapping deployments <!-- Thanks for sending a pull request! Here are some tips for you: 1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md 2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md 3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes --> **What this PR does / why we need it**: **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #24152 **Special notes for your reviewer**: cc @kubernetes/deployment **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 NONE ``` When looking for overlapping deployments, we should also find other deployments that select current deployment's pods, not just the ones whose pods are selected by current deployment. |
||
|---|---|---|
| .. | ||
| util | ||
| BUILD | ||
| deployment_controller.go | ||
| deployment_controller_test.go | ||
| progress.go | ||
| recreate.go | ||
| rollback.go | ||
| rolling.go | ||
| rolling_test.go | ||
| sync.go | ||
| sync_test.go | ||