- clusterGet should not return an error, if it cannot get the
loadbalancer config, as it's not critical
-> it should not rely on files created in nodehook actions
- this also fixes a nil pointer exception when cluster creation was
interrupted even before the loadbalancer was added to the cluster in
memory
Fixes#683
- generate node names when transforming from simple to cluster config
- ClusterCreate(clusterconfig) should have a ready made config and not
generate variables
- ClusterCreate() only prep LB if not already present (to be removed)
- cluster struct: serverloadbalancer is now of type LoadBalancer (Node +
Config)
- use new nodefilter syntax with 'id:index:suffix' instead of
'id[index]' everywhere
- use suffix when creating the LB
Excerpt:
- new version v1alpha3 with k3s extraArgs using node filters
- reflected in CLI via --k3s-arg
- new migration option to migrate (internally and via cli) from v1alpha2
to v1alpha3
- enhancements to how config files are being read
- e2e tests for config file migration
- generate node names when transforming from simple to cluster config
- ClusterCreate(clusterconfig) should have a ready made config and not
generate variables
- ClusterCreate() only prep LB if not already present (to be removed)
- cluster struct: serverloadbalancer is now of type LoadBalancer (Node +
Config)
- use new nodefilter syntax with 'id:index:suffix' instead of
'id[index]' everywhere
- use suffix when creating the LB
Excerpt:
- new version v1alpha3 with k3s extraArgs using node filters
- reflected in CLI via --k3s-arg
- new migration option to migrate (internally and via cli) from v1alpha2
to v1alpha3
- enhancements to how config files are being read
- e2e tests for config file migration
- LocalRegistryHostingConfigMap
- use localhost or docker-machine as external host IP
- fromContainerRuntime: user container-name + internal port
- registries.yaml: set up mirrors for both external and internal address
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