v5.9.0 #1675

@kravciak · 2026-06-02T14:41:13Z

github-actions[bot]
Bot Jun 2, 2026

What's Changed

Fix docker registry auth example by @kravciak in Fix docker registry auth example #1557
docs: show latest available k3s version by @AdrienHorgnies in docs: show latest available k3s version #1567
docs: add AdrienHorgnies as a contributor for doc by @allcontributors[bot] in docs: add AdrienHorgnies as a contributor for doc #1568
Use version sort for k3d version list output by @kravciak in Use version sort for k3d version list output #1554
chore: make function comments match function names by @tiaoxizhan in chore: make function comments match function names #1562
fix: files option for config on windows by @sofushn in fix: files option for config on windows #1582
Update the hardcoded k3s version from 1.21 to 1.32 by @lfrancke in Update the hardcoded k3s version from 1.21 to 1.32 #1589
chore(renovate): Add custom manager for k3s version tracking by @kobayashiyabako16g in chore(renovate): Add custom manager for k3s version tracking #1590
Skip DNS fix on Colima by @jtyr in Skip DNS fix on Colima #1595
Build process change by @yakom in Build process change #1606
feat(1406): introducing the option to match registry ports; by @yakom in feat(1406): introducing the option to match registry ports; #1607
feat([FEATURE] Add a --port-remove flag so nobody has to recreate their cluster with modified options #1570): introducing the --port-delete flag; by @yakom in feat(https://github.com/k3d-io/k3d/issues/1570): introducing the --port-delete flag; #1609
Fix Go Module badge by @kravciak in Fix Go Module badge #1616
bug([BUG] 5.9.0-rc0 ignores --registry-use on cluster create and tries to create default registry instead, which fails because of another problem #1617) : a change in the implementation of feat(1406); by @yakom in bug(https://github.com/k3d-io/k3d/issues/1617) : a change in the implementation of feat(1406); #1618
fix(registry): prevent --registry-use from triggering registry creation by @iwilltry42 in fix(registry): prevent --registry-use from triggering registry creation #1646
fix(entrypoint): skip drain/uncordon on agent nodes by @dpritchett in fix(entrypoint): skip drain/uncordon on agent nodes #1648
docs: update k3d-demo repo url by @isayme in docs: update k3d-demo repo url #1655
docs: fix md list issues by @isayme in docs: fix md list issues #1657
feat: cluster restart cmd, fix [FEATURE] Cluster Restart Command #984 by @isayme in feat: cluster restart cmd, fix #984 #1660
chore(deps): refresh deps + base images for v5.9.0 by @iwilltry42 in chore(deps): refresh deps + base images for v5.9.0 #1670
chore(deps): update dependency pymdown-extensions to v10.21.3 [security] by @renovate[bot] in chore(deps): update dependency pymdown-extensions to v10.21.3 [security] #1635

New Contributors

@AdrienHorgnies made their first contribution in docs: show latest available k3s version #1567
@tiaoxizhan made their first contribution in chore: make function comments match function names #1562
@sofushn made their first contribution in fix: files option for config on windows #1582
@lfrancke made their first contribution in Update the hardcoded k3s version from 1.21 to 1.32 #1589
@kobayashiyabako16g made their first contribution in chore(renovate): Add custom manager for k3s version tracking #1590
@dpritchett made their first contribution in fix(entrypoint): skip drain/uncordon on agent nodes #1648
@isayme made their first contribution in docs: update k3d-demo repo url #1655

Full Changelog: v5.8.3...v5.9.0

This discussion was created from the release v5.9.0.

bas-de-laine · 2026-06-23T18:06:19Z

bas-de-laine
Jun 23, 2026

Summary

k3d v5.9.0 causes DNS resolution failures in Colima v0.10.3 due to k3s automatically selecting 8.8.8.8 as the upstream resolver.

It might have something to do with PR #1595 which was merged in v5.9.0.

Workaround

Use the k3s --resolv-conf argument to point to a custom resolv.conf containing your internal DNS server.

Example k3d config:

apiVersion: k3d.io/v1alpha5
kind: Simple
volumes:
  - volume: ${K3D_X_RESOLV_CONF_FILE}:/etc/k3d/resolv.conf
    nodeFilters:
      - server:*
      - agent:*
options:
  k3s:
    extraArgs:
      - arg: "--resolv-conf=/etc/k3d/resolv.conf"
        nodeFilters:
          - server:*
          - agent:*

Root Cause

Since updating to v5.9.0, k3d running inside Colima v0.10.3 fails to resolve local addresses. Based on my understanding of the k3s documentation, k3s fails to find a suitable DNS because it detects the Docker loopback (127.0.0.11). It then injects a stub resolv.conf using 8.8.8.8.

Verification: Checking the coredns pod shows /etc/resolv.conf is set to 8.8.8.8, preventing resolution of local addresses (e.g., in my case, those resolved by 192.168.5.2 which is host.colima.internal).

Suggestion

This behavior might be worth documenting in the FAQ for users on Colima/Docker.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

v5.9.0 #1675

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

Uh oh!

v5.9.0 #1675

Uh oh!

github-actions[bot] Bot Jun 2, 2026

What's Changed

New Contributors

Replies: 1 comment

Uh oh!

bas-de-laine Jun 23, 2026

Summary

Workaround

Root Cause

Suggestion

github-actions[bot]
Bot Jun 2, 2026

bas-de-laine
Jun 23, 2026