mirrors/k3d
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
319 Commits 12 Branches 130 Tags
Commit Graph

156 Commits

Author SHA1 Message Date
iwilltry42
6e05342812
Merge branch 'master' of https://github.com/rancher/k3d into feature/add-node-command 2020-01-02 14:42:12 +01:00
iwilltry42
122ea4637a
wait for kubeconfig to be written when --wait is set 2020-01-02 14:37:27 +01:00
iwilltry42
469b56c253 replace 'default' with clustername in kubeconfig 2019-11-11 11:53:22 +01:00
iwilltry42
fbe93eb039 add more verbose error messages for getKubeconfig and Delete if no flag was set 2019-11-07 15:39:31 +01:00
iwilltry42
10179f8555 add warning for when agent arg is supplied without agents being created 2019-11-07 15:28:14 +01:00
Andy Zhou
3fd1061e8c
Merge pull request #137 from M3t0r/fix-127-0-0-1-not-replaced 
Fix kubeconfig not pointing to correct host when using docker-machine
 2019-11-04 11:56:14 -08:00
Simon Lutz Brüggen
2205264a11 Fix kubeconfig not pointing to correct host 
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?
```
 2019-11-04 17:29:39 +01:00
iwilltry42
e79c3a98d8 add init to worker as well (thanks for the hint @cbandy) 2019-11-04 09:49:22 +01:00
iwilltry42
b9ea408d49 Merge branch 'master' of https://github.com/rancher/k3d into feature/add-node-command 2019-10-21 08:12:48 +02:00
iwilltry42
6d771a20fa error exit if no clusters found 2019-10-21 07:35:07 +02:00
Thorsten Klein
1631a7b91a
Merge pull request #129 from ibuildthecloud/init 
Launch containers with init (thanks @ibuildthecloud)
 2019-10-19 09:21:25 +02:00
Darren Shepherd
b485682448 Launch containers with init 
k3s is not a child subreaper so running k3s as PID 1 will result
in zombie processes.  Using `docker run --init` works around this
issue.
 2019-10-18 22:10:44 -07:00
Darren Shepherd
645a5163d4 Only ignore get-kubeconfig error when !all 
If you are writing a script to launch k3s clusters checking the exit
code of `get-kubeconfig` is an easy way to tell if the kubeconfig is
available for use.
 2019-10-18 22:08:09 -07:00
Thorsten Klein
5c00056118
Merge pull request #121 from tw3n/get-kubeconfig-option-all 
Enable --all flag of get-kubeconfig (thanks to @tw3n )
 2019-10-10 10:49:01 +02:00
Xavier Hurst
836201611b Enable --all for get-kubeconfig 2019-10-09 21:43:51 +02:00
Cedric Kring
33c3f7cbda Use group values instead of keys for lookup 2019-10-09 19:51:24 +02:00
Cedric Kring
9b888c8216 Added support for group based node volume binds + refactoring 2019-10-09 19:35:13 +02:00
Cedric Kring
1e0aac19f6 Replace loop with simple append & spread 2019-10-05 12:30:08 +02:00
Cedric Kring
418c1887fe Allow volume binds to specific nodes with --volume src:dest@node-name 2019-10-05 11:44:45 +02:00
iwilltry42
9aa5af8d5d improve log level usage 2019-10-02 19:06:36 +02:00
Nicolas Lamirault
b5c4204303
Fix: use warningf 
Signed-off-by: Nicolas Lamirault <nicolas.lamirault@gmail.com>
 2019-10-01 14:42:28 +02:00
Nicolas Lamirault
44d6fef28c
Update: use log level instead of errorf 
Signed-off-by: Nicolas Lamirault <nicolas.lamirault@gmail.com>
 2019-10-01 10:15:24 +02:00
Nicolas Lamirault
61107ca5bf
Update: use log level 
Signed-off-by: Nicolas Lamirault <nicolas.lamirault@gmail.com>
 2019-09-28 19:58:05 +02:00
iwilltry42
95c62650fa remove unused constants 2019-09-26 08:49:26 +02:00
iwilltry42
80f5aa7d58 add todo 2019-09-26 08:40:16 +02:00
iwilltry42
1fabe118fa only allow adding worker nodes for now 2019-09-26 08:24:15 +02:00
Nicolas Lamirault
3631e65570
Update: replace log with logrus 
Signed-off-by: Nicolas Lamirault <nicolas.lamirault@gmail.com>
 2019-09-25 22:41:00 +02:00
iwilltry42
0317cc395b add --volume flag to add-node command 2019-09-06 12:12:32 +02:00
iwilltry42
f33fa2d4cc move global constants to types.go 2019-09-06 11:55:22 +02:00
iwilltry42
487418974e remove --all flag for ls 2019-09-06 11:47:25 +02:00
iwilltry42
ee1eb58466 fix passing args to add-node node 2019-09-06 11:37:13 +02:00
iwilltry42
e4e7a32e0d operate on clusterspec for reusability 2019-09-06 11:21:04 +02:00
iwilltry42
3e80e37faf allow connections to non-dockerized k3s clusters 2019-09-04 18:10:08 +02:00
iwilltry42
c8f8fdb139 add addNode function with basic functionality 2019-09-04 18:10:08 +02:00
iwilltry42
89ba0f67b7 use --port/-p for publishing ports now instead of api-port 2019-09-04 18:09:36 +02:00
iwilltry42
53eba1828d remove 'create --version' flag 2019-09-04 18:09:35 +02:00
iwilltry42
d6364af32c add add-node command 2019-09-04 18:09:35 +02:00
misakwa
29204d18a5 Address review comment 2019-08-05 21:14:43 -05:00
misakwa
4e52afd578 Add agent-arg and pass through to container 2019-07-30 23:08:40 -05:00
iwilltry42
205a521c81 go mod tidy 2019-07-30 10:36:49 +02:00
wxdao
058bb1d9e4 Use client.WithAPIVersionNegotiation() 2019-07-25 06:42:31 +00:00
wxdao
c1263487a5 Upgrade docker sdk 2019-07-25 03:15:28 +00:00
Thorsten Klein
c5e5adb0e2
Merge pull request #91 from rancher/feature/import-images-helper 
[Feature] import images from docker daemon into k3d using a helper container
 2019-07-23 19:26:01 +02:00
iwilltry42
96c883a10a cleanup tools container using defer 2019-07-17 09:32:46 +02:00
iwilltry42
081ec611bc --keep flag to not remove the tarball after import 2019-07-11 15:43:49 +02:00
iwilltry42
a4c75c6568 use a tools container 2019-07-10 18:23:47 +02:00
iwilltry42
07e458d6f1 test 2019-07-08 09:59:01 +02:00
iwilltry42
036a8a9fd0 Merge branch 'feature/load-images' of https://github.com/rancher/k3d into feature/load-images 2019-07-08 09:58:33 +02:00
iwilltry42
f670dde640 test 2019-07-08 09:58:26 +02:00
Ubuntu
4bde59702d error should occur when current time is after start+timout 2019-07-04 02:12:40 +00:00