Little helper to run CNCF's k3s in Docker
sigs.k8s.io/yaml
everywhere in the project to allow for consistent json/yaml output (#1094)k3d config init
used the legacy config format (#1091)Full Changelog: https://github.com/k3d-io/k3d/compare/v5.4.3...v5.4.4
In command k3d registry create
k3d registry create --proxy-remote-url https://registry-1.docker.io -p 5000 -v /tmp/registry:/var/lib/registry
In config file:
# ...
registries:
create:
name: docker-io # name of the registry container
proxy:
remoteURL: https://registry-1.docker.io # proxy DockerHub
volumes:
- /tmp/reg:/var/lib/registry # persist data locally in /tmp/reg
config: | # tell K3s to use this registry when pulling from DockerHub
mirrors:
"docker.io":
endpoint:
- http://docker-io:5000
See registry documentation
Full Changelog: https://github.com/k3d-io/k3d/compare/v5.4.2...v5.4.3
hostAliases
in the config fileregistries.create.image
(same as k3d registry create --image
) in config v1alpha4
(no version bump) (#1056)Full Changelog: https://github.com/k3d-io/k3d/compare/v5.4.1...v5.4.2
Full Changelog: https://github.com/k3d-io/k3d/compare/v5.4.0...v5.4.1
Note: This is the first independent release of k3d
Note 2: You can now fund the work on k3d using GitHub Sponsors (@iwilltry42) or IssueHunt (k3d-io/k3d)
buildx
& buildx bake
for multiplatform builds (instead of VMs with the according architectures)k3d node create --k3s-arg
flag (#1032)bridge
mode for k3d-created networks for Podman compatibility (#986)This release was automatically tested with the following setups:
Expected to Fail with the following versions:
We test a full cluster lifecycle with different K3s channels, meaning that the following list refers to the current latest version released under the given channel:
Expected to Fail with the following versions:
Full Changelog: https://github.com/k3d-io/k3d/compare/v5.3.0...v5.4.0
Note: Now trying to follow a standard scheme defined by https://keepachangelog.com/en/1.0.0/
--volume/-v
flag that k3d automatically expands
k3s-storage
-> /var/lib/rancher/k3s/storage
k3s-manifests
-> /var/lib/rancher/k3s/server/manifests
k3s-manifests-custom
-> /var/lib/rancher/k3s/server/manifests/custom
(not K3s default: this is just some sub-directory inside the auto-deploy manifests directory which will also be parsed)k3s-containerd
-> /var/lib/rancher/k3s/agent/etc/containerd/config.toml
(use with caution, K3s generates this file!)k3s-containerd-tmpl
-> /var/lib/rancher/k3s/agent/etc/containerd/config.toml.tmpl
(used by K3s to generate the real config above)k3s-registry-config
-> /etc/rancher/k3s/registries.yaml
(or just use --registry-config
)k3d-
prefix will now be created and managed by k3d
k3d.io/v1alpha3
is now deprecated in favor of k3d.io/v1alpha4
cmd/util
, does not affect the CLI (#916)This release was automatically tested with the following setups:
Expected to Fail with the following versions:
We test a full cluster lifecycle with different K3s channels, meaning that the following list refers to the current latest version released under the given channel:
Expected to Fail with the following versions:
Full Changelog: https://github.com/rancher/k3d/compare/v5.2.2...v5.3.0
Full Changelog: https://github.com/rancher/k3d/compare/v5.2.1...v5.2.2