This repository was archived by the owner on Jan 11, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 546
add GPU ExtendedResourceToleration admission controller support #3181
Merged
jackfrancis
merged 19 commits into
Azure:master
from
lachie83:feat-add-gpu-ExtendedResourceToleration
Jun 27, 2018
Merged
Changes from all commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
c5594e7
check for kubernetesConfig nil (#3164)
jackfrancis a36be0c
add GPU ExtendedResourceToleration admission controller support
lachie83 f39f29b
Revert "check for kubernetesConfig nil (#3164)"
lachie83 e9f061e
Update condition to match review
lachie83 2511e6f
Update conditionals to match both N series and device plugin
lachie83 c9e6dc1
Add toleration to run kube-proxy on tainted gpu nodes
lachie83 9e8fa64
Update Nvidia gpu device plugin to upstream ds example
lachie83 50b46a4
Update docs
lachie83 a8df245
Add support for 1.11
lachie83 83034c1
cleanup k8s_version_test
jackfrancis e91bc93
add nvidia.com/gpu to addons
jackfrancis bbc2c7a
Revert "add nvidia.com/gpu to addons"
lachie83 2ea4097
remove register node with taints
lachie83 6b7af96
Revert "Add toleration to run kube-proxy on tainted gpu nodes"
lachie83 b1b087a
Merge branch 'master' into feat-add-gpu-ExtendedResourceToleration
lachie83 478f39f
fixed rebase errors
lachie83 474d0e6
fix formatting errors
lachie83 cb1486e
fixed tests
lachie83 be6ebd7
actually check for nvidia addon enabled
jackfrancis File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
30 changes: 23 additions & 7 deletions
30
parts/k8s/addons/kubernetesmasteraddons-nvidia-device-plugin-daemonset.yaml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -35,14 +35,14 @@ write_files: | |
| "log-opts": { | ||
| "max-size": "50m", | ||
| "max-file": "5" | ||
| }{{if IsNVIDIADevicePluginEnabled}} | ||
| }{{if IsNSeriesSKU .}}{{if IsNVIDIADevicePluginEnabled}} | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Let's figure out how to simplify these guards.
I infer the answer to #2 is "no" based on the way this has been implemented here. For #1, if the answer to that is also "no", then we should combine these two checks: basically, we should get rid of IsNVIDIADevicePluginEnabled, or we should have IsNVIDIADevicePluginEnabled only return true if it's on an N Series node.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
| ,"default-runtime": "nvidia", | ||
| "runtimes": { | ||
| "nvidia": { | ||
| "path": "/usr/bin/nvidia-container-runtime", | ||
| "runtimeArgs": [] | ||
| } | ||
| }{{end}} | ||
| }{{end}}{{end}} | ||
| } | ||
| {{end}} | ||
|
|
||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Since you are adding the toleration, can you also replace the snippet from below at
/etc/docker/daemon.json"inkubernetesagentcustomdata.ymlsince we want it to be enabled for GPU pools only but not for CPU pools.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.
Fixed