also,

1. run in container is false
2. onedev and kubernete server are different VM
3. agent installed on kubernete VM and it is working well

Seems that OneDev can not find kubectl in system path for some reason. Please specify absolute path to kubectl to see if it works.

Let me explain in detail, minikube is working but the bash command does not see the full path or anything I give as an alias, it acts as if it is in a container.

also I run some basic commands like alias, ls -a, systemctl.

commands results.

alias -> gave empty ( but there is lot of alias)

ls -a -> gave files of the project

systemctl -> gave working services ( I saw minikube working but not found for full path or alias)

I see you are runing commands on an agent. The agent is not aware of k8s, it simply runs command with VM's shell (if you are running agent directly on VM), or inside the container (if you are running agent inside container). I can not understand why you are mentioning minikube here.

The point I want to say is that remote shell is not working properly. kubectl, minikube, k3s, I will create a new VM, maybe there is a problem with VM.

update

18:56:09 error: error validating "k8s.yml": error validating data: failed to download openapi: Get "http://localhost:8080/openapi/v2?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused; if you choose to ignore these errors, turn validation off with --validate=false

How are you running the build agent?

Hi Robin, Finally I resolve all bugs and issues. There are lot of workaround I has been applied. I will write an article on Medium about it and share my experience as a developer. Thanks for your kind help.

Note: I will share the Medium article link here after write.

That will be great. Thank you!