Fix kubeconfig not pointing to correct host when using docker-machine #137
Conversation
This file contains 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
The kubeconfig generated by docker.io/rancher/k3s:v0.10.2 or earlier sets the cluster.server address to 127.0.0.1. Previously this seems to have been localhost. And we only replace localhost with the correct address for our local kubeconfig. The error this can lead to: ``` $ k3d --version k3d version v1.3.4 $ docker-machine --version docker-machine version 0.16.1, build cce350d7 $ docker --version Docker version 19.03.1, build 74b1e89 $ k3d create INFO[0000] Created cluster network with ID 649d6f34b84a4df16d2524f0ea0ce69cd4f964a79ae56e2a07bb1ee11d1fce50 INFO[0001] Add TLS SAN for 192.168.99.100 INFO[0001] Created docker volume k3d-k3s-default-images INFO[0001] Creating cluster [k3s-default] INFO[0001] Creating server using docker.io/rancher/k3s:v0.10.2... INFO[0001] Pulling image docker.io/rancher/k3s:v0.10.2... INFO[0018] SUCCESS: created cluster [k3s-default] INFO[0018] You can now use the cluster with: export KUBECONFIG="$(k3d get-kubeconfig --name='k3s-default')" kubectl cluster-info $ export KUBECONFIG="$(k3d get-kubeconfig --name='k3s-default')" $ kubectl cluster-info To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'. The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port? ```
andyz-dev
approved these changes
Nov 4, 2019
|
Any ETA on a new release containing this fix? Currently I'm patching around it with a quick bash script, but it'd be nice to have. |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
The kubeconfig generated by
docker.io/rancher/k3s:v0.10.2or earlier sets thecluster.serveraddress to127.0.0.1. Previously this seems to have beenlocalhost. And we only replacelocalhostwith the correct address for our local kubeconfig.The error I encountered: