github k3d-io/k3d v1.2.0

latest releases: v5.6.3, v5.6.2, v5.6.1...
4 years ago

What changed?

  • [FEATURE]: New Flags for k3d create:
    • --publish/--add-port [ip:][host-port:]container-port[/protocol][@node-specifier]
      • only container-port is mandatory
      • the node-specifier is set to server by default
        • it can be either a descriptor from server/master, workers and all or a full name of a node (e.g. k3d-k3s-default-worker-1)
        • if you choose to map the same container-port from more than one container to the host, you can make use of the --port-auto-offset X flag which will automatically choose the host-port based on the provided offset
  • [CHANGE]: --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
    • --port/-p will have the new functionality as of v2.0.0
  • [ENHANCEMENT] no empty list and more meaningful cluster status table
  • [CHANGE] --volume/-v is now a string-slice, so it has to be provided for each extra volume-mount
  • [BUGFIXES] no cluster name conflicts or accidental deletions of clusters
  • [ENHANCEMENT] clean up docker volumes upon cluster deletion
  • [ENHANCEMENT] Makefile fixed and now usable on more platforms (had problems on Mac)
  • several more refactorings, bugfixes, enhancements

Thanks

  • to @andyz-dev for becoming our new very active collaborator!
  • to @andyz-dev and @zeerorg for several bugfixes and enhancements
  • to @goffinf and @mash-graz for the very beneficial discussions on the port mapping issue
  • to everyone who actively contributed to the project via PRs and opening new issues, filing bugreports, etc.

Thanks for the nice and helpful feedback!

There are many more fixes and enhancements and features coming, so stay tuned :)

Don't miss a new k3d release

NewReleases is sending notifications on new releases.