19 Commits (64e52360a8809e381781b4efefece9632ae7073c)

Author	SHA1	Message	Date
iwilltry42	f73fe36eb0	change/docs: copyright notice year	11 months ago
iwilltry42	93a67d712e	change: golangci-lint fix whitespaces	1 year ago
Simon Emms	c1d8e307f1	Fix deleting of cluster by config file (#1054)	2 years ago
Thorsten Klein	852df7786a	[Migration] search and replace rancher/k3d with k3d-io/k3d in most places (#976)	3 years ago
iwilltry42	a8f937fa01	fix: clusterDelete: properly parse config file to avoid failure on v1alpha4	3 years ago
Thorsten Klein	3b0e6990c4	license: - 2022 (#943)	3 years ago
iwilltry42	7710f33686	license: - 2022	3 years ago
kuritka	4ffc71d4be	Removing non-existing cluster via configuration ... Signed-off-by: kuritka <kuritka@gmail.com>	3 years ago
iwilltry42	7073a8fad7	migrate to module rancher/k3d/v5	3 years ago
iwilltry42	91426eabd1	cmd: make config initialization more general ... - move viper initialization from k3d config file to separate util sub-package in cmd/ - use that new subpackage init function to leverage the config file in `k3d cluster delete` - cover that with an e2e test case	3 years ago
Mateusz Urbanek	917c19eae5	feat(logging): using new package containing logrus.Logger instead of global scope logrus (closes #583) (#699, @Shanduur)	3 years ago
iwilltry42	6c94d7db3d	overall/license: update to year range -2021	3 years ago
iwilltry42	7b8506b1d9	fix: proper handling of registries and networks when deleting clusters/nodes	4 years ago
Thorsten Klein	185ffcd34f	[Enhancement] clusterDelete: proper node and network handling (#437) ... This comes with several fixes/improvements - only consider containers that have the default object label (app=k3d) - handle network deletion - check if there are other k3d containers connected - if there are only registries, disconnect them - if there are non-registry nodes, leave everything as it is - if there are any containers connected, that are not automatically disconnected, log a warning and continue	4 years ago
Thorsten Klein	ecc025b35e	[Feature] Registry for v4 & Restructure Cluster Creation (#334)	4 years ago
iwilltry42	d7b25ac6ab	v3 -> v4	4 years ago
iwilltry42	a385241c77	clusterDelete: no error if no cluster was found (fixes #379)	4 years ago
iwilltry42	b02c783130	adjust toplevel pkg functions to new syntax	4 years ago
iwilltry42	08f7a47119	new syntax for cluster creation and kubeconfig manipulation	4 years ago
iwilltry42	40a2d032ab	deleteCluster: only warn about failed kubeconfig deletion if file exists and couldn't be deleted	4 years ago
iwilltry42	c00f8952ba	getKubeconfig: write to new file by default	4 years ago
iwilltry42	76d90478f5	Go Module: use v3 for go module compatibility	4 years ago
iwilltry42	d3f7621ed8	completion: use AvailableClusters completion for start, stop, delete, getKubeconfig	4 years ago
iwilltry42	21fd427d8a	maintenance: cleanup debug logs	4 years ago
iwilltry42	639daef7fb	Reorder parameters ... - runtimes.Runtime should at max. the second function parameter (right after context.Context)	4 years ago
iwilltry42	0d2c22455d	Overall: use context.Context in top-level exported functions ... - package cluster: use context.Context as first function param in every exported function - package cmd: pass cmd.Context() to calls to package cluster exported functions	4 years ago
iwilltry42	2d68ef12e4	deleteCluster: remove cluster details from kubeconfig ... - refactoring in pkg/cluster/kubeconfig - new functions to delete a cluster from kubeconfig - call RemoveClusterFromDefaultKubeConfig after deleting cluster	4 years ago
iwilltry42	4a8e155f51	use global selectedRuntime variable instead of parsing the flag in every subcommand	5 years ago
iwilltry42	bc49f197d9	cleanup and prepare for push to rancher/k3d	5 years ago
iwilltry42	8aad61a39a	improve usage texts	5 years ago
iwilltry42	098fe0803c	implement start/stop for nodes and clusters	5 years ago
iwilltry42	1e33e0de8c	add deleteCluster functionality	5 years ago
iwilltry42	7063d62508	initial implementation of 'get clusters'	5 years ago
iwilltry42	8eb9832298	delete cluster	5 years ago
iwilltry42	95c28f298c	add subcommands	5 years ago
iwilltry42	bdcdbd817a	init cobra	5 years ago
misakwa	4e52afd578	Add agent-arg and pass through to container	5 years ago
iwilltry42	081ec611bc	--keep flag to not remove the tarball after import	5 years ago
iwilltry42	deccb0122a	enable importing multiple images at once	5 years ago
iwilltry42	ab2c54ca1d	add import-image command for importing single image	5 years ago
Andy Zhou	f037e1b225	Deprecate --timeout, shift shot hand options around ... We have been giving user warnings about --timeout going away for a while. Now fully deprecate it. Use -t for --wait option Move -w from --wait to --workers. Many users of K3d generate multi-node clusters, -w will make their life easier.	5 years ago
Andy Zhou	1565e43365	Modify --api-port to take a stirng argument ... --api-port only takes the port as argument. This patch modifies it to take a string argument, in the form of host:port.	5 years ago
iwilltry42	f771dcf8b5	shell flag text	5 years ago
iwilltry42	eb5b88052e	add auto mode for shell based on SHELL env var and support zsh	5 years ago
Andy Zhou	abd9a984eb	Add --shell argument ... Add subshell argument --shell. Currently, support only bash, which is also the default value.	5 years ago
Andy Zhou	d63f7d4bf2	Rename bash command to shell ... @iwilltry42 suggested to group all shell support under and single subcommand -- shell.	5 years ago
Andy Zhou	2971dd6845	Add the ability to execute commands directly with the bash subcommand ... In addition to provide an interactive shell, this patch adds the '--command' and '-c' options to allow user to issue a command in the context of a cluster. For example: $ k3d bash -c 'kubectl cluster-info'	5 years ago
Andy Zhou	4ef6710e22	Add basic bashShell() function ... Add the basic frame work for supporting spawning a bash shell by cli command. With this change, we can spawn a bash shell in the context of a cluster $ k3d create -n my-cluster $ k3d bash -n my-cluster [my-cluster] $> // execute commands with KUBECONFIG already set up [my-cluster] $> kubectl get pods	5 years ago
Andy Zhou	b9713c4ac4	Add --auto-restart flag for the create command ... When creating clusters with the --auto-restart flag, any running cluster will remain "running" up on docker daemon restart. By default, without this flag, a "running" cluster becomes "stopped" after docker daemon restart. Clusters stopped with 'k3d stop' command will remain stopped after docker daemon restart regardless the settings of this flag.	5 years ago
Andy Zhou	3683eeb181	Deprecate the --timeout option ... Use --wait <timeout> instead	5 years ago