Elastic-operator fails to spin up ES cluster

Elastic Orchestration Elastic Cloud on Kubernetes (ECK)
1

Hello,

I've installed eck-operator using all-in-one.yaml example (https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-deploy-eck.html). It started ok, but constantly complains in logs (verbosity=1):

E0113 16:47:58.885664       1 reflector.go:178] pkg/mod/k8s.io/client-go@v0.18.6/tools/cache/reflector.go:125: Failed to list *v1.Secret: stream error when reading response body, may be caused by closed connection. Please retry. Original error: stream error: stream ID 865; INTERNAL_ERROR
I0113 16:49:30.669670       1 trace.go:205] Trace[668989355]: "Reflector ListAndWatch" name:pkg/mod/k8s.io/client-go@v0.18.6/tools/cache/reflector.go:125 (13-Jan-2021 16:48:30.668) (total time: 60001ms):
Trace[668989355]: [1m0.001093298s] [1m0.001093298s] END

Creation of quickstart cluster, using https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-deploy-elasticsearch.html example, just creates Elasticsearch resource but no pods or secrets or other artifacts. It looks that operator ignores this definition or just can't find it.

K8s cluster is AWS EKS, version 1.16, supporting set of other resources and services. Any help is appreciated.

2

It looks like a connectivity issue between ECK and the control plane, or an error in the API Server. Can you provide the logs from the API server ?