Skip to content

Commit a024b8b

Browse files
authoredSep 16, 2022
docs:Troubleshooting note on stale pricing data (#2503)
1 parent c201b33 commit a024b8b

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed
 

‎website/content/en/preview/troubleshooting.md

+11
Original file line numberDiff line numberDiff line change
@@ -358,3 +358,14 @@ spec:
358358
karpenter.sh/discovery: karpenter-demo
359359
ttlSecondsAfterEmpty: 30
360360
```
361+
## Stale pricing data on isolated subnet
362+
363+
The following pricing-related error occurs if you are running Karpenter in an isolated private subnet (no Internet egress via IGW or NAT gateways):
364+
365+
```text
366+
ERROR controller.aws.pricing updating on-demand pricing, RequestError: send request failed
367+
caused by: Post "https://api.pricing.us-east-1.amazonaws.com/": dial tcp 52.94.231.236:443: i/o timeout; RequestError: send request failed
368+
caused by: Post "https://api.pricing.us-east-1.amazonaws.com/": dial tcp 52.94.231.236:443: i/o timeout, using existing pricing data from 2022-08-17T00:19:52Z {"commit": "4b5f953"}
369+
```
370+
This network timeout occurs because there is no VPC endpoint available for the [Price List Query API.](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/using-pelong.html).
371+
To workaround this issue, Karpenter ships updated on-demand pricing data as part of the Karpenter binary; however, this means that pricing data will only be updated on Karpenter version upgrades.

0 commit comments

Comments
 (0)
Please sign in to comment.