mirrors/k3d
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
370 Commits 12 Branches 130 Tags 31 MiB
3e12d67da3
Commit Graph

370 Commits

This Branch
This Branch
All Branches
Author SHA1 Message Date
iwilltry42
dc4c29361f
return error if no image was specified for import 2020-01-03 15:51:28 +01:00
Thorsten Klein
8a65268312
Merge pull request #102 from rancher/feature/add-node-command 
[Feature] `add-node` command and deprecation cleanup
 2020-01-02 14:47:35 +01:00
iwilltry42
97bebbad66
add note to add-node command 2020-01-02 14:42:53 +01:00
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
Thorsten Klein
0eaaef4c45
Merge pull request #158 from chrisjohnson/add-example-non-trusted-ca 
Fix up examples, remove unnecessary port reference and use $HOME so t…
 2019-12-24 15:43:27 +01:00
Chris Johnson
f9fe8ef0c1 Fix up examples, remove unnecessary port reference and use $HOME so the examples are mac compatible 2019-12-24 09:39:27 -05:00
Thorsten Klein
99d6a18be7
Merge pull request #157 from chrisjohnson/add-example-non-trusted-ca 
Add example for non-publicly-trusted CA (thanks @chrisjohnson )
 2019-12-24 13:36:19 +01:00
Chris Johnson
b1b7e957bc Add example for non-publicly-trusted CA 2019-12-23 20:33:29 -05:00
iwilltry42
c3b799c6e2 add registry.yaml to docs (thanks @pojntfx) 2019-11-22 08:01:08 +01:00
iwilltry42
469b56c253 replace 'default' with clustername in kubeconfig 2019-11-11 11:53:22 +01:00
iwilltry42
576ac040cc add note about kubectl 2019-11-08 10:27:26 +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
iwilltry42
8079d7d2be exclude .local 2019-11-07 14:41:57 +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
3b0c095765 add examples for all k3s versions to use a private registry 2019-11-04 10:16:58 +01:00
Thorsten Klein
85b19f7ef7
Merge pull request #135 from fearoffish/update-insecure-registry-example 
Update the documentation template for the insecure registry example to be compatible with k3s v0.10.0+ (thanks @fearoffish)
 2019-11-04 10:07:45 +01:00
iwilltry42
dc19eb7139 add section about 'NodeHasDiskPressure' issues to FAQ 2019-11-04 10:00:24 +01:00
iwilltry42
e79c3a98d8 add init to worker as well (thanks for the hint @cbandy) 2019-11-04 09:49:22 +01:00
iwilltry42
9b8fcd17be Merge branch 'master' of https://github.com/rancher/k3d into feature/add-node-command 2019-11-03 19:52:17 +01:00
iwilltry42
18a3db3d9b remove outdated docs and add simple version command 2019-10-30 15:55:03 +01:00
Jamie van Dyke
02b80fecfc Update the documentation with an up to date template for the insecure registry example 2019-10-29 21:07:51 +00:00
iwilltry42
e22299f485 update version in readme 2019-10-21 14:32:18 +02:00
iwilltry42
6ad5a7b9dd clarify homebrew section 2019-10-21 14:31:57 +02: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
Andy Zhou
e7b372f0fd
Merge pull request #127 from docwhat/patch-1 
readme: add brew install instructions
 2019-10-20 04:02:04 -07:00
Christian Höltje
c25618cbdc readme: add brew install instructions 2019-10-19 16:12:55 -04: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
Thorsten Klein
fb74afceff
Merge pull request #128 from ibuildthecloud/master 
Only ignore get-kubeconfig error when !all (thanks @ibuildthecloud)
 2019-10-19 09:18:05 +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
iwilltry42
36bda94dbd clarify example 2019-10-17 08:07:03 +02:00
iwilltry42
f3e2ef5508 link faq to example 2019-10-15 10:46:44 +02:00
Thorsten Klein
9f56c006ee
Merge pull request #124 from zer0def/anyfs 
Provide an example that allows running k3d on filesystems k3s doesn't like. (thanks to @zer0def)
 2019-10-15 10:43:41 +02:00
zer0def
6bdcb3f7f9 Provide an example that allows running k3d on filesystems k3s doesn't like, like btrfs or tmpfs. 2019-10-12 23:47:04 +02:00
iwilltry42
89cb12181a add --timestamp global flag for log formatting 2019-10-11 10:48:15 +02:00
iwilltry42
d11b96ac7e use golangci-lint v1.20 2019-10-10 11:41:31 +02:00
iwilltry42
af0f30c8d4 reduce number of travis builds to a single one on go1.13.x 2019-10-10 10:59:40 +02: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
Thorsten Klein
b09a9680e6
Merge pull request #116 from cedrickring/add-node-specifier 
Add node-specifier for volumes (thanks to @cedrickring )
 2019-10-10 10:38:58 +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
Thorsten Klein
0d01441553
Merge pull request #117 from tw3n/master 
makefile: consistent use of go option (thanks to @tw3n )
 2019-10-06 19:26:56 +02:00
Xavier Hurst
81748f9b3a makefile: consistent use of go option 2019-10-06 17:43:16 +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