-
Notifications
You must be signed in to change notification settings - Fork 407
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
feat: improve hostNetwork mode of NodePool by adding NodeAffinity to pods with specified annotation (#1935) #1959
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1959 +/- ##
==========================================
- Coverage 52.41% 52.37% -0.04%
==========================================
Files 173 174 +1
Lines 21015 20972 -43
==========================================
- Hits 11014 10985 -29
+ Misses 9051 9039 -12
+ Partials 950 948 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
542c5a7
to
eb92417
Compare
/rerun |
@huangchenzhao filter hostnetworkpropagation also should be removed. |
…pods with specified annotation (openyurtio#1935)
eb92417
to
44ad71e
Compare
Quality Gate passedIssues Measures |
removed |
/lgtm |
…pods with specified annotation (openyurtio#1935) (openyurtio#1959)
…pods with specified annotation (openyurtio#1935) (openyurtio#1959)
What type of PR is this?
What this PR does / why we need it:
A mutating webhook is introduced in yurt-manager component for adding NodeAffinity to pods with
annotation["apps.openyurt.io/exclude-host-network-pool"] = true
. The NodeAffinity indicates that the pods don't want to be scheduled to nodes in hostNetwork mode NodePool.Users should add
annotation ["apps.openyurt.io/exclude-host-network-pool"] = true
manually to pods if they don't want to run pods on edge nodes in hostNetwork mode nodepool.Which issue(s) this PR fixes:
Fixes #1935