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.
Describe your changes
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.
Issue ticket number and link
Ref https://github.com/spinkube/runtime-class-manager/issues/48
Checklist before requesting a review