kubefire create cluster demo fails - kubelet.service 404

[mjbright]

Describe the bug
Running kubefire cluster create demo fails when attempting to enable kubelet.service

The problem seems to be the hardcoded URL https://raw.githubusercontent.com/kubernetes/release/v0.16.3/cmd/kubepkg/templates/latest/deb/kubelet/lib/systemd/system/kubelet.service which returns a 404 Not Found (apparently - not actually seen in the log)

To Reproduce
To reproduce kubefire create cluster demo

Observe the curl command curl -sSL https://raw.githubusercontent.com/kubernetes/release/v0.16.3/cmd/kubepkg/templates/latest/deb/kubelet/lib/systemd/system/kubelet.service

Try this in a browser or command line - not 404 Not Found.

Expected behavior
At this precise step, then kubelet service should be enabled.
Bottom line is of course that a kubeadm cluster should be successfully created.

Environment

• OS version

PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

• Kubefire version

Version: v0.3.10
Build: 35cb33b-20230416001838

• Kubefire runtime info

CONTAINERD	IGNITE 	CNI   	RUNC 	CNIPLUGIN                 
v1.6.20   	v0.10.0	v1.1.1	1.1.6	0.4.0/kubefire-cni-bridge

Additional context
Looks like bitrot of the kubernetes/release repo ... structural change ?

Specifying k3s as bootstrapper creates a k3s based cluster successfully, presumably this problem touches only the default kubeadm bootstrapper.

[sousmangoosta]

I got same issue, I edited file .kubefire/bootstrappers/v0.3.10/kubeadm/v1.28.4.yaml to bypass
I changed kube_release_version: v0.16.4 to kube_release_version: v0.16.2 for version: v1.28.4
They removed kubepkg on version v0.16.3