docs: add k3s use case guide#311
Draft
OndrejDrapalik wants to merge 2 commits into
Draft
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
/docs/use-cases/k3sguide for the officiale2b/k3stemplateSandboxAPI andcommands.runkubectl port-forwardandgetHostDependencies
e2b/k3sis published for public use.Validation
mintlify validatemintlify broken-links9121d260) under a temporary private tagThe docs explicitly poll for the Node and CoreDNS objects before waiting for their Ready conditions because PR #49 currently gates sandbox creation on Kubernetes API readiness only.