v4.0.0-rc.2

v4.0.0-rc.2

Preliminary Changelog: main-v4/CHANGELOG.md#v400

• Note, that the lifecycle hooks are not yet accessible via the CLI

Changes since last release (v4.0.0-rc.1)

• NEW (module): NodeDeleteOpts & ClusterDeleteOpts
• fix: make --all work properly for k3d node delete and k3d registry delete
• NEW (flag): k3d node delete --all --registries to also consider registries when deleting nodes (they're a special node type)
• change (module): nodes now have a list of networks instead of a single reference (to improve registry handling)
• fix: properly handle registries and networks when deleting clusters

v4.0.0-rc.1

v4.0.0-rc.1

Preliminary Changelog: main-v4/CHANGELOG.md#v400

• Note, that the lifecycle hooks are not yet accessible via the CLI

Changes since last release (v4.0.0-rc.0)

• fix: auto-restart registry (like clusters)
• NEW: k3d cluster create --registry-config /my/registries.yaml
  • will be merged with the auto-generated registries config when you also use --registry-create or --registry-use
  • config file allows embedding the registries.yaml in the Simple config (see docs)
• fix: LocalRegistryHosting.v1 config map now uses localhost or docker-machine ip for the host field

v4.0.0-rc.0

v4.0.0-rc.0

Preliminary Changelog: main-v4/CHANGELOG.md#v400

• Note, that the lifecycle hooks are not yet accessible via the CLI

Changes since last release (v4.0.0-beta.0)

• [DOCS] Add Chocolatey install option (#443, @erwinkersten)
• tests/e2e: add E2E_INCLUDE and rename E2E_SKIP to E2E_EXCLUDE
• registry: only warn, if configmap couldn't be created in any node, as one is enough.
• [Enhancement] Improved listings for nodes & registries (#439, @inercia)

v4.0.0-beta.0

v4.0.0-beta.0

Preliminary Changelog: main-v4/CHANGELOG.md#v400

• Note, that the lifecycle hooks are not yet accessible via the CLI

Changes since last Alpha (v4.0.0-alpha.2)

• flag syntax: noun-action everywhere: --kubeconfig-merge-default
• updated documentation/readme -> https://k3d.io
• spell checking (#434, @jsoref)
• fix: some nil-pointers, e.g. when exposing a port on the loadbalancer when it was disabled via flag
• new default k3s version (as fallback in edge cases)
• fix: proper handling of networks upon cluster deletion in the light of having registries around that connect to cluster networks
• LocalRegistryHostingV1 from KEP-1755

v4.0.0-alpha.2

v4.0.0-alpha.2

Preliminary Changelog: main-v4/CHANGELOG.md#v400

• Note, that the lifecycle hooks are not yet accessible via the CLI

Changes since last Alpha

• k3d cluster create --registry-use REGNAME works now
  • e.g. k3d registry create myreg followed by k3d cluster create --registry-use k3d-myreg
  • for now only tested with registries running in docker

v4.0.0-alpha.1

-> Preliminary Changelog: https://github.com/rancher/k3d/blob/main-v4/CHANGELOG.md#v400
Note, that the lifecycle hooks are not yet accessible via the CLI and the k3d cluster create --registry-use flag is still hidden as not fully implemented yet.

v4.0.0-alpha.0

v4.0.0-alpha.0

First preview release of k3d v4

v3.4.0

v3.4.0

Features & Enhancements

• Enable the restart policy unless-stopped which should have been enabled since the very beginning (#413, @fabricev)
• add new k3d cluster list --output yaml|json flag to format the list output in YAML or JSON format (#416, @inercia)
  • teaser: this is the preparation for something super cool 😎

Fixes

• Allow escaping literal @ in flags that use node filters via \@
  • "literal" meaning, that this is not the @ sign indicating that a node filter is following (#412)

Infrastructure

• fix install script error with wget (#414, @bashofmann)

Misc

• code: pin hardcoded fallback k3s version to v1.19.4-k3s1
• docs: use Python 3.9 for building mkdocs page (#415, @cclaus)
• ci: allow building artifacts from main-* and release-* branches

---

Announcement

With some larger changes coming in soon (config file and registry support), we've done some refactoring in k3d code leading to the need of increasing the major version. So watch out for k3d v4 dropping soon 4️⃣ 🎉

v3.4.0-test.0: Config File Alpha Test

Pre-Release to test #351

Use config files via k3d cluster create --config /path/to/config.yaml

Example Config File:

apiVersion: k3d.io/v1alpha1
kind: Simple
name: test
servers: 1
agents: 2
exposeAPI:
  hostIP: "0.0.0.0"
  port: "6443"
image: rancher/k3s:latest
volumes:
  - volume: /tmp:/tmp/somepath
    nodeFilters:
      - all
ports:
  - port: 80:80
    nodeFilters:
      - loadbalancer
  - port: 0.0.0.0:443:443
    nodeFilters:
      - loadbalancer
env:
  - envVar: bar=baz
    nodeFilters:
      - all
labels:
  - label: foo=bar
    nodeFilters:
      - server[0]
      - loadbalancer

options:
  k3d:
    wait: true
    timeout: "60s"
    disableLoadbalancer: false
    disableImageVolume: false
  k3s:
    extraServerArgs:
      - --tls-san=127.0.0.1
    extraAgentArgs: []
  kubeconfig:
    updateDefaultKubeconfig: true
    switchCurrentContext: true

v3.3.0

v3.3.0

Features

• Add back the -e/--env flag to add environment variables (now uses nodefilters like the other similar flags, including --label, --volume, ..)

Misc

• some cleanup