Create ephemeral cluster with k3d/k3s

[akyriako]

##What Added an option for k3d/k3s clusters

##Why An alternative flavor to kind

##How Based on the existing cluster/cluster-up/kind/common.sh script logic, with the necessary minor changes to facilitate k3d

##Tested On Linux ubuntu2214 5.15.0-48-generic

##Anything else The original common.sh script creates an artefact in [manifests/kubernetes/deployment.yaml , line 124] by adding an additional trailing "-host" every time the script is being executed. Eventually, it ends up with a pretty long "proc-host-host-host-etc-etc" value for hostPath.path (mitigated for k3d common.sh)

[SamYuan1990]

thanks for contribution. em... may I know any change on CI as adding github action with k3s as k8s provider?

[rootfs]

@akyriako thank you for the contribution! Can you break the PR into two? One for the k3d cluster, that is independent and can get merged quickly. The second is to change the deployment manifests used by integration test and add the k3d to the CI.

[SamYuan1990]

enabled CI for this PR.

[SamYuan1990]

I agree with @rootfs that this PR should not configure the CI....

I made some arguments about this in a previous comment.

ok, if so, I suppose just keep it pass with current CI with KIND, and let's have another PR for k3s in CI maybe?

[marceloamaral]

Both kind and k3d creates kuberntes cluster. So we should test only one. Microshift on the other hand, creates OpenShift cluster and this should be a useful test.