ci(.github): update helm-chart-smoketest with more k8s variations

[vdice]

Describe your changes

• Updates the helm install smoke test with more k8s flavors! Here we add minikube, microk8s and k3d
• Since they run in parallel, I figured running all cases both on PRs and merges to main is fine for now -- thoughts?

These distros all had GH actions ready-to-use. For other distros we'd like to cover under test (k0s, etc), we could either craft a reusable action in-house and stick to the same matrix-based approach added here... or maybe break out into separate workflows.

• Depends on fix(detect.go): check default location only after distro-specific #264 (microk8s specifically)
  • (See successful runs on fork which incorporates PR#264 alongside this commit)

Issue ticket number and link

Ref #48

Checklist before requesting a review

• I have performed a self-review of my code
• If it is a core feature, I have added thorough tests.
• I tested the changes with the following distributions:
  • Kind
  • MiniKube
  • MicroK8s
  • K3s
  • Rancher RKE2
  • Azure AKS
  • GCP GKE (Ubuntu nodes)
  • AWS EKS (AmazonLinux2 nodes)
  • AWS EKS (Ubuntu nodes)
  • Digital Ocean Kubernetes

[voigt]

Looking forward to merge this after #264 is merged!

[vdice]

Weird, currently getting the following from the shim-downloader just from the k3d cluster:

2025-03-17T18:02:12	INFO	start downloading shim from  https://github.com/spinframework/containerd-shim-spin/releases/download/v0.18.0/containerd-shim-spin-v2-linux-x86_64.tar.gz...
gzip: invalid magic
tar: Child returned status 1
tar: Error is not recoverable: exiting now

Trying to figure out the underlying cause...

[voigt]

Weird, currently getting the following from the shim-downloader just from the k3d cluster:

2025-03-17T18:02:12	INFO	start downloading shim from  https://github.com/spinframework/containerd-shim-spin/releases/download/v0.18.0/containerd-shim-spin-v2-linux-x86_64.tar.gz...
gzip: invalid magic
tar: Child returned status 1
tar: Error is not recoverable: exiting now

Trying to figure out the underlying cause...

Feels like the downloaded file got corrupted... Maybe it would be a good idea to add a bit more verbose info to the downloader script...

Some ideas:

• removing the -s from curl to get filesize
• adding an ls -lah to check filesize
• print md5sum

Generally, printing curl and tar version wouldn't hurt either...

[vdice]

I added some debug lines; oddly, I'm seeing variable behavior. (Still only occuring for k3d; the other clusters all succeed.) Sometimes the shim is downloaded just fine and the provisioner proceeds with installation, other times the last log line seen is 'INFO start downloading shim from ...' and the provisioner container is still pending, almost like the download is hanging.

Going to try to repro with a k3d cluster locally and see what I can find...

[vdice]

@voigt ok, ready for a re-review. The issue with k3d was due to #371; I've pinned the k8s version to 1.32.1 for the time being.

Do we want any or all of the debug info added to the download_shim.sh script?

[voigt]

Uh! That was a nasty one. Great that you'll join figured it out!

IMO we should keep the debug info.