Little helper to run CNCF's k3s in Docker

dockerkubernetesgoclusterrancherk3dk3s

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

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		3 years ago
..
actions	[Enhancement] Edit CoreDNS ConfigMap on disk for more reliability (#814)	3 years ago
client	[Cleanup] Types, ready-log-messages & closing connections (#818)	3 years ago
config	config: fix failing v1alpha2 -> v1alpha3 migration (#799)	3 years ago
logger	feat(logging): using new package containing logrus.Logger instead of global scope logrus (closes #583) (#699, @Shanduur)	3 years ago
runtimes	[Cleanup] Types, ready-log-messages & closing connections (#818)	3 years ago
types	[Cleanup] Types, ready-log-messages & closing connections (#818)	3 years ago
util	[Enhancement] Edit CoreDNS ConfigMap on disk for more reliability (#814)	3 years ago