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
The idea here would be to expose a gauge metric like karpenter_cloudprovider_offering_available with labels instance_type, capacity_type, and zone.
This metric would be set to 1 for all offerings that Karpenter is aware are available from the cloud provider. If the cloudprovider changed its mind about the availability of the offering (i.e. for AWS, there is an ICE [Insufficient Capacity Error] when launching an instance) then the gauge would be exposed as 0
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
N/A
Are you currently working around this issue?
N/A
Additional Context
No response
Attachments
No response
Community Note
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
The text was updated successfully, but these errors were encountered:
Tell us about your request
This idea was originally proposed by @bwagner5.
The idea here would be to expose a gauge metric like
karpenter_cloudprovider_offering_available
with labelsinstance_type
,capacity_type
, andzone
.This metric would be set to 1 for all offerings that Karpenter is aware are available from the cloud provider. If the cloudprovider changed its mind about the availability of the offering (i.e. for AWS, there is an ICE [Insufficient Capacity Error] when launching an instance) then the gauge would be exposed as 0
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
N/A
Are you currently working around this issue?
N/A
Additional Context
No response
Attachments
No response
Community Note
The text was updated successfully, but these errors were encountered: