v2.4.0 bump to k3d v5.4.6

Bump k3d to v5.4.6

k3d-action	k3d	k3s
v2.4.0	v5.4.6	rancher/k3s:v1.24.4-k3s1

What's Changed

• rename action.yaml -> action.yml by @jkremser in #42
• Allow-listing the action.yml in .licignore by @jkremser in #43
• Set k3d v5.4.6 as default k3d version by @somaritane in #46
• Revert "rename action.yaml -> action.yml" by @somaritane in #47
• Revert "Allow-listing the action.yml in .licignore" by @somaritane in #48

New Contributors

• @jkremser made their first contribution in #42

Full Changelog: v2.3.0...v2.4.0

v2.3.0 bump to k3d v5.4.1

Bump k3d to v5.3.0

k3d-action	k3d	k3s
v2.3.0	v5.4.1	rancher/k3s:v1.22.7-k3s1 or set image explicitly

v2.2.0 bump to k3d v5.3.0

Bump k3d to v5.3.0

k3d-action	k3d	k3s
v2.2.0	v5.3.0	rancher/k3s:v1.22.6-k3s1 or set image explicitly

v2.1.0 k3d-version argument

• k3d-version parameter allowing to specify concrete k3d version (@arkadius)
  • see documentation
• k3d version bump 5.1.0 -> 5.2.2 (@arkadius)

k3d-action	k3d	k3s
v2.1.0	v5.2.2	rancher/k3s:v1.21.7-k3s1 or set image explicitly

v2.0.0 Lightweight

k3d has started to natively support registry import and networking. For this reason, there is no longer a need for k3d-action to continue to provide this functionality.

Thanks to this, k3d-action has become much lighter and does not need to support some extra arguments.

Breaking changes

• deprecated network argument (see k3d docs for replacement)
• deprecated subnet-CIDR argument (see k3d docs for replacement)
• deprecated use-default-registry argument (see k3d docs for replacement)
• deprecated registry-port argument (see k3d docs for replacement)

k3d-action@v2 supports k3d@v5 and higher.

Check our documentation on how to use k3d-action

Upgrade to k3d v4.4.7

The last GitHub action release Ubuntu Version: 20210628.1 failed to successfully run the k3d-action.
For this reason we had to create a fix PR in k3d, which allows us to continue using the k3d-action.

Besides upgrading the k3d-action in your workflow, it is also necessary to upgrade the k3s version.
I recommend leaving the default k3s version, see table below.

k3d-action	k3d	k3s
v1.5.0	v4.4.7	rancher/k3s:v1.21.2-k3s1 or set image explicitly

Possibility to set k3s image

• K3d-action users set k3s version explicitly via configuration or argument e.g.--image docker.io/rancher/k3s:v1.20.5-k3s1 otherwise k3d specifies which version will be used.

• K3d-action uses k3d v4.4.1

k3d-action	k3d	k3s
v1.4.0	v4.4.1	specified by k3d or set image explicitly

For further details read:

• documentation
• possibility to override k3s image

Breaking changes

No breaking changes

v1.3.1

k3d-action	k3d	k3s
v1.1.0	v3.4.0	rancher/k3s:v1.20.2-k3s1
v1.2.0	v4.2.0	rancher/k3s:v1.20.2-k3s1
v1.3.0	v4.2.0	rancher/k3s:v1.20.4-k3s1

• Mechanism waiting until agents are ready (#14), fixed for a case when kubelets are not yet ready.
• Fix README.md [registry-port] (#15)
• Bump k3s from v1.20.2-k3s1 to v1.20.4-k3s1

v1.3.0

k3d-action	k3d	k3s
v1.1.0	v3.4.0	rancher/k3s:v1.20.2-k3s1
v1.2.0	v4.2.0	rancher/k3s:v1.20.2-k3s1
v1.3.0	v4.2.0	rancher/k3s:v1.20.4-k3s1

• Mechanism waiting until agents are ready (#14)
• Fix README.md [registry-port] (#15)
• Bump k3s from v1.20.2-k3s1 to v1.20.4-k3s1

support k3d v4.2.0

k3d-action	k3d	k3s
v1.1.0	v3.4.0	rancher/k3s:v1.20.2-k3s1
v1.2.0	v4.2.0	rancher/k3s:v1.20.2-k3s1

• migration to k3d v4.2.0
• Registry support
  • customize local registry port

      - uses: AbsaOSS/[email protected]
        id: single-cluster
        name: "Create single Cluster with Registry"
        with:
          cluster-name: "test-cluster-1"
          use-default-registry: true
          registry-port: 5080
          args: >-
            --agents 1

• Config file upport
  • you can configure action via config files or mix k3d arguments together with config files

      - uses: AbsaOSS/[email protected]
        id: single-cluster
        name: "Create single k3d Cluster"
        with:
          cluster-name: "test-cluster-1"
          args: >-
            --agents 1
            --config=<path to config yaml>