f8f17caf78
- 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 |
||
|---|---|---|
| .. | ||
| fixes | ||
| k3s | ||
| k8s | ||
| defaults.go | ||
| env.go | ||
| images.go | ||
| intent.go | ||
| k3slogs.go | ||
| loadbalancer.go | ||
| node.go | ||
| registry.go | ||
| types.go | ||