v1.2.0-beta.1
Pre-release
Pre-release
Beta-Release for PR #43
Changes:
--publish
/--add-port
syntax is now[ip:][host-port:]container-port[/protocol]@node-specifier
, where container-port and node-specifier are mandatory and node-specifier can be one or multiple- node-specifier can be either one of
all
,server
,worker
or the name of a node that will be created (easier naming will follow, since e.g.k3d-some-test-name-worker-0
is not convenient to use) - since the node-specifier is mandatory, we won't automatically map ports to multiple nodes
- node-specifier can be either one of
--api-port
/-a
is now the default to set the K8s ApiPort mapping, since we want to re-use--port
/-p
for the functionality of--publish
/--add-port
- You can toggle/set a automatic port offset for mapping the same container-port from multiple worker nodes to predictable host-ports using the new
--port-auto-offset X
flag with X > 0.- if a multi-node portmapping is specified (e.g.
--publish 1234:4321@workers
) without the auto offset flag set, the docker API will return an error due to colliding ports
- if a multi-node portmapping is specified (e.g.