k3d/cmd/cluster
Thorsten Klein f8f17caf78
[Cleanup] Types, ready-log-messages & closing connections (#818)
- new special internal role `initServer` used only to determine the correct ready-log-message
- ready-log-messages now looked up by role and new `Intent` type (cluster-create/cluster-start/node-create/node-start), as especially for the init server there are different log messages indicating that we can proceed with the next step
- moving types around:
	- K3s env vars now under .../types/k3s/env.go
	- defaults now under .../types/defaults.go
	- ...
- improved waiting for log messages
	- not checking the whole log again and again in a loop
	- follow log with a single reader (and retry in case we see a fatal error, meaning that the K3s container will restart -> backoff after 10 tries)
	- BREAKING: new `*runtimeTypes.NodeLogsOpts` parameter in GetNodeLogs
2021-10-27 12:56:04 +02:00
..
cluster.go chore(cmd): add subcommands in one call (#819) 2021-10-27 09:43:10 +02:00
clusterCreate.go [Fix] more resilient post-create cluster preparation (DNS) (#780) 2021-10-13 17:36:42 +02:00
clusterDelete.go migrate to module rancher/k3d/v5 2021-09-07 08:58:57 +02:00
clusterEdit.go migrate to module rancher/k3d/v5 2021-09-07 08:58:57 +02:00
clusterList.go migrate to module rancher/k3d/v5 2021-09-07 08:58:57 +02:00
clusterStart.go [Cleanup] Types, ready-log-messages & closing connections (#818) 2021-10-27 12:56:04 +02:00
clusterStop.go migrate to module rancher/k3d/v5 2021-09-07 08:58:57 +02:00