docs: Add Karpenter integration guide for Chainguard VMs #2713
Conversation
This file contains hidden or 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
Co-authored-by: Patrick Smyth <[email protected]> Signed-off-by: Erika Heidi <[email protected]>
Co-authored-by: Patrick Smyth <[email protected]> Signed-off-by: Erika Heidi <[email protected]>
Co-authored-by: Patrick Smyth <[email protected]> Signed-off-by: Erika Heidi <[email protected]>
Co-authored-by: Patrick Smyth <[email protected]> Signed-off-by: Erika Heidi <[email protected]>
✅ Deploy Preview for ornate-narwhal-088216 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
[ ] Check if this is a typo or other quick fix and ignore the rest :)
Type of change
Adding new documentation for Chainguard VM integration with Karpenter
What should this PR do?
This addresses the gap between the official Karpenter documentation (which focuses on standard AMIs) and the specific requirements for custom AMI integration. The documentation is based on real customer implementation experience and includes practical troubleshooting steps that aren't covered in the official Karpenter documentation, particularly around IAM permissions and AMI verification.
Why are we making this change?
A customer testing Chainguard EKS node VMs encountered challenges integrating with Karpenter autoscaler. I noticed that the current docs lack guidance for using Chainguard VMs with Karpenter.
What are the acceptance criteria?
How should this PR be tested?