Releases: twz123/k0s
Releases · twz123/k0s
v1.28.2+k0sriscv64.0
This is an experimental k0s build based on k0s v1.28.2+k0s.0 that supports RISC-V. Related k0s issue: k0sproject#1919.
A default cluster setup should work. Unit tests pass, and some of the integration tests as well:
- check-backup
- check-basic
- check-capitalhostnames
- check-configchange
- check-customca
- check-customports-dynamicconfig
- check-customports
- check-disabledcomponents
- check-extraargs
- check-hacontrolplane
- check-hostnameoverride
- check-metrics
- check-multicontroller
- check-noderole-no-taints
- check-noderole-single
- check-noderole
- check-psp
- check-singlenode
- check-statussocket
What definitely doesn't work:
- Anything Calico
- Anything dual-stack, since it requires Calico
- Node-local load balancing
--enable-metrics-scraper
- Bundled OpenEBS storage
- probably more...
In order to make Kubernetes work on RISC-V, this binary uses some non-standard multi-arch OCI images:
- quay.io/twz123/coredns:1.11.1-1@sha256:ef304af35da98ff9f1af445b103b3fd73221ffaddb802be152cd0c488ec19699
- quay.io/twz123/apiserver-network-proxy-agent:v0.1.4-1@sha256:66a0ce4a1b7f98ea74510d30c1e96d80846c9a233b9c6eb30143d32209e127a3
- quay.io/twz123/kube-proxy:v1.28.2-1@sha256:77dbd9bb0b9ee748b4d39f0e998076cd1269ae097b482fd58f54dea56906efe1
- quay.io/twz123/kube-router:v1.6.0-iptables1.8.9-1@sha256:7ddbda29726da778945274ede6ff530351c6075695779777486d6ecc5ce8ea58
- quay.io/twz123/cni-node:1.3.0-k0s.1@sha256:c08c83a7388bd3d92637846603d7065871b2c7e59f4a0de1e701c1045a1215ea
- quay.io/twz123/metrics-server:v0.6.4-1@sha256:ee0d5a55b6724d4a955aaa5357d655092f4e4d1458f92e1b5d79d9fd127073d0
- quay.io/twz123/pause:3.9-1@sha256:266cc1ad730c2a1adc10a60e7b6216ad13095ec5b0329336a557141306ec4625
The binaries are signed with my GPG key (FE33A2282371E831
) and the custom OCI images are pulled using their hash.