A GitHub Action to run lightweight ephemeral Kubernetes clusters during workflow. Fundamental advantage of this action is a full customization of embedded k3s clusters. In addition, it provides a private image registry and multi-cluster support.
APACHE-2.0 License
Bot releases are hidden (Show)
Bump k3d to v5.4.6
k3d-action | k3d | k3s |
---|---|---|
v2.4.0 | v5.4.6 | rancher/k3s:v1.24.4-k3s1 |
Full Changelog: https://github.com/AbsaOSS/k3d-action/compare/v2.3.0...v2.4.0
Published by kuritka over 2 years ago
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 |
Published by kuritka over 2 years ago
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 |
Published by kuritka almost 3 years ago
k3d-action | k3d | k3s |
---|---|---|
v2.1.0 | v5.2.2 | rancher/k3s:v1.21.7-k3s1 or set image explicitly |
Published by kuritka almost 3 years ago
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.
network
argument (see k3d docs for replacement)subnet-CIDR
argument (see k3d docs for replacement)use-default-registry
argument (see k3d docs for replacement)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
Published by kuritka over 3 years ago
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 |
Published by kuritka over 3 years ago
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:
No breaking changes
Published by kuritka over 3 years ago
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 |
registry-port
] (#15)Published by kuritka over 3 years ago
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 |
registry-port
] (#15)Published by kuritka over 3 years ago
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 |
- 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
- 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>
Published by kuritka over 3 years ago
k3d-action | k3d | k3s |
---|---|---|
v1.1.0 | v3.4.0 | rancher/k3s:v1.20.2-k3s1 |
Published by kuritka almost 4 years ago