Lorry used to have a k8s exec client, which invokes lorry container through kubectl's exec capabilities. It is useful in local debug, as we often run kubeblocks as a process (with go run commands) instead of building an image and running as a pod.
In kb-agent, this exec client is missing and local debug becomes more complicated. I suggest add back exec client.
Using port forward to achieve the same functionality seems to be better, as it reuses the HTTP client. (So that we don't need to deal with things like escaping quotes)
Lorry used to have a k8s exec client, which invokes lorry container through kubectl's exec capabilities. It is useful in local debug, as we often run kubeblocks as a process (with
go run
commands) instead of building an image and running as a pod.In kb-agent, this exec client is missing and local debug becomes more complicated. I suggest add back exec client.