-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Local registry: only attach network if missing #2601
Local registry: only attach network if missing #2601
Conversation
0134680
to
cc84ee8
Compare
thanks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for this! 😅
much cleaner than I hoped, some nits 😅
The example script for creating a kind cluster with a local registry will connect the container to the "kind" network. The first time the local registry is created, this is fine and is what is needed. On subsequent runs to create new clusters, if the local registry container has already been set up, the command to attach to the "kind" network will emit an error message to the create output that can be confusing. This updates the example script to do a basic check of the registry containers network configuration. If the kind network appears to be already connected, then the script will not attempt to connect it again. Signed-off-by: Sean McGinnis <[email protected]>
cc84ee8
to
90eef3a
Compare
https://deploy-preview-2601--k8s-kind.netlify.app/docs/user/local-registry/ looks like it was about the scrollbox, but we can follow-up, this is a good change to land. thank you! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder, stmcginnis The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The example script for creating a kind cluster with a local registry
will connect the container to the "kind" network. The first time the
local registry is created, this is fine and is what is needed. On
subsequent runs to create new clusters, if the local registry container
has already been set up, the command to attach to the "kind" network
will emit an error message to the create output that can be confusing.
This updates the example script to do a basic check of the registry
containers network configuration. If the kind network appears to be
already connected, then the script will not attempt to connect it again.
Fixed: #2600