Add SchedulingConfig for Enhanced GPU and Pod Affinity Scheduling #7
Conversation
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
Update crd manifests Since I used higher level controller-gen, it introduces additional changes, I do not want to fallback to lower version because our cluster is actually in v1.28 which requires higher version.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
SchedulingConfigStruct,GPUTypeandAffinityWorkloadis used to support the pod affinity targeting. These values will be assgined todeploymenttemplatesnodeAffinityandpodAffinityhas been added for GPU and workload (vllm) colocation. (It will be pending if workload is not ready)checkKubernetesVersionForSchedulerto unblock deployment for higher kubernetes versions. the API are compatible, it's safe the bump the version.What do these changes do?
Related issue number
Fixes #issue number