Repository navigation
docs(imageless-kubernetes): FloxHub login prereq + schema-aware runtime key - #139
Open
stephenyeargin wants to merge 1 commit into
Open
stephenyeargin wants to merge 1 commit into
stephenyeargin wants to merge 1 commit into
Conversation
…e runtime key Add a Prerequisites section to the kind demo page — Flox installed plus `flox auth login` — and explain that `just up` creates the FloxHub-token secret for you and stops if you are not logged in. Previously the page jumped straight to `just up`, which now fails fast without a login. Clarify in troubleshooting that the containerd runtime plugin id depends on the config schema version (`io.containerd.grpc.v1.cri` for v2, `io.containerd.cri.v1.runtime` for v3/4), cross-referencing self-managed. Refs DEV-417. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
barstoolbluz
approved these changes
Oct 26, 2026
This branch was successfully deployed
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
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.
What
Documentation updates from the containerd-shim-flox maintenance (DEV-351 / DEV-414), per DEV-417.
examples/kind-demo.mdx— add a Prerequisites section: Flox installed andflox auth login. The page previously jumped straight toflox activate -- just up, but the demo now requires a FloxHub login —just upcopies your token into a Kubernetes secret and fails fast if you're not logged in. Links to Configuration for how that secret is created and mounted.install/troubleshooting.mdx— clarify in the "Pods stuck inContainerCreating" steps that the containerd runtime plugin id is schema-version dependent (io.containerd.grpc.v1.crifor configversion = 2,io.containerd.cri.v1.runtimeforversion = 3/4), cross-referencing self-managed. Prevents misreading a correct config on newer containerd as "missing."Why
Verifying the demo end-to-end on the released 1.1.0 shim surfaced that the public kind-demo page omitted the FloxHub login step a reader now needs, and the troubleshooting page only showed the legacy CRI key.
Checks
valeclean (0 errors/warnings/suggestions) on both files./install-flox/install,/man/flox-auth,/imageless-kubernetes/config,/imageless-kubernetes/install/self-managed).Out of scope
install/eks.mdxregisters only under the legacygrpc.v1.crikey; confirming whether EKS needs thecri.v1.runtimekey depends on the EKS AMI's containerd config schema. Folded into DEV-349 (validate EKS support with current containerd versions).Refs DEV-417.
🤖 Generated with Claude Code