Example: Kubernetes with KinD¶
You may need to access Kubernetes within your build. KinD is a popular option, and easy to run in an action.
Certified for:
-
x86_64
-
arm64
including Raspberry Pi 4
Use a private repository if you're not using actuated yet
GitHub recommends using a private repository with self-hosted runners because changes can be left over from a previous run, even when using Actions Runtime Controller. Actuated uses an ephemeral VM with an immutable image, so can be used on both public and private repos. Learn why in the FAQ.
Try out the action on your agent¶
Create a new file at: .github/workspaces/build.yml
and commit it to the repository.
Note that it's important to make sure Kubernetes is responsive before performing any commands like running a Pod or installing a helm chart.
name: build
on: push
jobs:
start-kind:
runs-on: actuated
steps:
- uses: actions/checkout@master
with:
fetch-depth: 1
- name: get arkade
uses: alexellis/setup-arkade@v1
- name: get kubectl and kubectl
uses: alexellis/arkade-get@master
with:
kubectl: latest
kind: latest
- name: Create a KinD cluster
run: |
mkdir -p $HOME/.kube/
kind create cluster --wait 300s
- name: Wait until CoreDNS is ready
run: |
kubectl rollout status deploy/coredns -n kube-system --timeout=300s
- name: Explore nodes
run: kubectl get nodes -o wide
- name: Explore pods
run: kubectl get pod -A -o wide
- name: Show kubelet logs
run: docker exec kind-control-plane journalctl -u kubelet
To run this on ARM64, just change the actuated label to actuated-aarch64
.