You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction
to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do
not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Description
The InPlacePodVerticalScaling feature gate is crucial for the Kube Startup CPU Boost operator. Without this feature gate enabled, the operator will increase POD resources without the possibility to revert them back when needed. Therefore, the operator should validate if the InPlacePodVerticalScaling is enabled.
NOTE: this is interim solution until InPlacePodVerticalScaling graduates to beta.
There is no perfect way to programmatically validate if a feature gate is enabled cluster wide. The most straightforward but not perfect solution is to use /metrics/ API that eventually consistent.
Community Note
to the original issue to help the community and maintainers prioritize this request
not help prioritize the request
Description
The
InPlacePodVerticalScaling
feature gate is crucial for the Kube Startup CPU Boost operator. Without this feature gate enabled, the operator will increase POD resources without the possibility to revert them back when needed. Therefore, the operator should validate if theInPlacePodVerticalScaling
is enabled.NOTE: this is interim solution until
InPlacePodVerticalScaling
graduates to beta.There is no perfect way to programmatically validate if a feature gate is enabled cluster wide. The most straightforward but not perfect solution is to use
/metrics/
API that eventually consistent.References
The text was updated successfully, but these errors were encountered: