CI action error due to inaccessibility of k8s cluster

[alphaX86]

Description

Meshery SMP Action is failing on some CI runs due to inaccessibility of k8s cluster present in the workflow

Expected Behavior

The error must be rectified and CI run should be free of errors

[gyohuangxin]

@alphaX86 Thank you very much.

[gyohuangxin]

@alphaX86 oops, the actions failed: https://github.com/layer5io/meshery-smp-action/actions/runs/3407625025/jobs/5667478085#step:3:79

[alphaX86]

From the logs it shows that it didn't have permission to extract files 😭 oh damn.... Should we try an alternative CI function for this? Or shall we wait for subsequent CI action runs to see results?

[gyohuangxin]

@alphaX86 I give you the maintain access to this repo, you can run a configurable benchmark test on self-hosted runner if it works.

[alphaX86]

👀👀 ok, will do 👍

[gyohuangxin]

@alphaX86 Do you have any updates?

[alphaX86]

I ran the CI action on the repo and checked. Seems its an error on the permissions for extracting installation files during k8s setup. IDK what exactly causes this. I referred this in net and as per the suggestions I even re-ran the action. No joy :/

Likely we might need to change the k8s action to test it. What's your opinion? @gyohuangxin

[gyohuangxin]

@alphaX86 Please go ahead, the only difference is the version of manusa/actions-setup-minikube, so IMO maybe you can research what's changeed in the new version.

[alphaX86]

For CIL cluster, seems it's restricted to use actions within it. Similar error is also caused in this repo I saw...
engineerd/setup-kind#13
Seems manual method is the way for solving in case of self-hosted runners :/

NVM, I think I got a mere idea now

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.