[codex] Add k3d registry support#1
Draft
suin wants to merge 1 commit into
Draft
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
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.
Summary
Adds k3d as a Kubernetes-ready distribution alongside kind, including registry detection and restore-time registry handling.
Changes
k8s: kind|k3d/--k8s=kind|k3dconfiguration and CLI flow.REGISTRYfor the restored VM Docker daemon.local-registry-hostingso tools such as Tilt can use local registry auto-detection.examples/k3dandexamples/tiltsamples.Impact
Users can now choose k3d for spind Kubernetes-ready environments and use a k3d local registry from the
DOCKER_HOSTprinted by spind. Tilt users can rely on k3d local registry auto-detection without addingdefault_registry()to the Tiltfile.Validation
task checktask e2ebunx oxfmt --check .../../bin/spind upfromexamples/k3dafter fixing the k3d sample readiness wait