fix(local-dev): add Kind config and registry startup to fix image pull #189
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.
This PR fixes the broken local development setup for running the plugin with Kind and a local registry (registry.dev:5000).
Changes made:
Added a kind-config.yaml with containerdConfigPatches to configure registry.dev:5000 as an insecure mirror.
Included insecure_skip_verify = true to allow Kind to pull from the local registry without TLS.
Modified scripts/run.sh to start the local Docker registry before attempting to push and load the image into Kind.
Result:
With these changes, the plugin runs successfully in a Kind cluster, and the pod pulls the image correctly without ErrImagePull. Verified by observing expected logs from the plugin pod.
Issue (#188)