Some problem with stolon init

Hello, Simone, I’ve checked and didn’t found any exact problems that I have -
If talking without prehistory I’m trying to deploy stolon into kubernetes baremetal cluster and initialization with docker one-shot command produced output like

cannot get cluster data: failed to get latest version of configmap: Get “”: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

Seems like it is api problem, BUT I “curled” other sections of api, particularly - /api/v1/namespaces/default/configmaps/ and it works, but there was no configmap stolon-cluster-kube-stolon. I’m not sure what is a logic in init - does it have to create this configmap or it have to exist on the init stage. This is not the first “incarnation” on this servers, but I think that I cleared everything from previous installation of k8s and stolon.
Actually I just wanna hear an answer about init logic and advice - do I have to re-create kubernetes cluster and retry init or I have to dig into some other parts like initdb work?