Support running in an in-cluster self-hosted worker without separately setting context about k8s-deploy HOT 8 CLOSED

@koushdey inorder to support this, perhaps we could change the logic of throwing the error into a warning instead.

from k8s-deploy.

@koushdey My actions runner is running in a pod in a Kubernetes cluster. That pod is running on a service account that has the required access. If I were to run kubectl commands in that pod, they would use the Kubernetes credentials supplied to the pod by Kubernetes and succeed. k8s-set-context with the service account method asks for information that is not relevant or which I do not have in this use case.

from k8s-deploy.

@N-Usha Any chance you had a look into it?

from k8s-deploy.

This issue is idle because it has been open for 14 days with no activity.

from k8s-deploy.

@japsu For running kubectl cmds we need to set context. How will you authenticate the kubectl cmds? k8s-set-context makes use of service account as well to set this context. Have you considered using this action?

from k8s-deploy.

@koushdey so this way, when you convert this check into a warning, kubectl cli tool would float up the failures related to lack of k8s context.

from k8s-deploy.

This issue is idle because it has been open for 14 days with no activity.

from k8s-deploy.

Changes are merged. Closing issue

from k8s-deploy.