Support setting the deployment strategy in Profiles #1215
Merged
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.
Description
Update types, clientset and CRDs to support setting the deployment strategy for functions using Profiles.
Why is this needed?
Support for changing the deployment strategy type is required to update functions using GPUs in a cluster with limited GPU availability.
Who is this for?
What company is this for? Are you listed in the ADOPTERS.md file?
How Has This Been Tested?
New types where used in the pro fork of faas-netes where the support for Profiles is implemented.
Changes for the OpenFaaS chart were verified while testing this feature with faas-netes pro.
Types of changes
Checklist:
git commit -s