docs:Troubleshooting note on stale pricing data #2503
Merged
+11
−0
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
✅ Deploy Preview for karpenter-docs-prod ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
There is a workaround, there's an isolated vpc command line option that will disable the pricing loookups. On mobile or I would link it, but it's in the docs. |
jonathan-innis
requested changes
Sep 13, 2022
chrisnegus
commented
Sep 14, 2022
jonathan-innis
requested changes
Sep 14, 2022
I'll see if I can find that link and describe that as a workaround. |
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.
Fixes Issue #2485
Description
This PR updates troubleshooting docs to note that clusters on a private subnet are unable to access pricing data because no VPC endpoint is available to get that data. The result is an error message noting that existing pricing data will be used.
Does this change impact docs?