Refactor GPU Operator Support #127
Merged
Conversation
This file contains 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
spjmurray
force-pushed
the
refactor_gpu_operators
branch
2 times, most recently
from
90849c8
to
98375bc
Compare
This reduces the Kubernetes API interface down to "please install autoscaler/GPU or not". The actual logic is delegated to the controller proper that's able to make the intelligent descision based on presence of a workload pool that requires the feature, and specifics of that flavor. While in the area, I've removed the CAPO specific hacks from the K8S API and pushed them down into the `clusteropenstack` provisioner where they belong, likewise scheduling hints for the autoscaler.
spjmurray
force-pushed
the
refactor_gpu_operators
branch
from
98375bc
to
43677ca
Compare
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.
This reduces the Kubernetes API interface down to "please install autoscaler/GPU or not". The actual logic is delegated to the controller proper that's able to make the intelligent descision based on presence of a workload pool that requires the feature, and specifics of that flavor. While in the area, I've removed the CAPO specific hacks from the K8S API and pushed them down into the
clusteropenstackprovisioner where they belong.