ECK compatibility with Docker for Windows (Kubernetes)

Elastic Orchestration Elastic Cloud on Kubernetes (ECK)
1

Hi,

Someone could tell me if I can install ECK with Docker for Windows (compliance) ?

Thx.

PS: I have this error.

"logger":"transport","message":"Skipping pod because it has no IP yet","ver":"1.0.0-beta1-84792e30","namespace":"default","pod_name":"quickstart-es-default-0"}

Events:
Type Reason Age From Message

Warning FailedScheduling 67s (x2 over 67s) default-scheduler pod has unbound immediate PersistentVolumeClaims

2

We have not tested on Windows but my assumption would be that it should work. Based on the information you provided it seems there is a problem with scheduling and binding your PersistentVolumeClaims.

It might also be helpful to get some debugging information around PersistentVolumes and PersistenVolumeClaims and the exact manifests your are using (I am assuming the quickstart example from our docs?)

kubectl describe pod quickstart-es-default-0 
kubectl describe pvc elasticsearch-data-quickstart-es-default-0

and

kubectl describe pv $PV_ID_FROM_PREVIOUS_COMMAND

See also https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-troubleshooting.html for more troubleshooting tips.

Maybe you could try to deploy a cluster with emptyDir first to see if this is your only problem, see https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-volume-claim-templates.html

3

You helped me a lot because I had not thought about checking this command.

kubectl describe pvc elasticsearch-data-quickstart-es-default-0

So, my bad, I force a custom storage-class, not declared in my K8s.

After remove my custom storage-class, use default settings from ECK.

Message

  • waiting for a volume to be created, either by external provisioner "docker.io/hostpath" or manually created by system administrator
  • External provisioner is provisioning volume for claim "default/elasticsearch-data-quickstart-es-default-0"
  • Successfully provisioned volume pvc-f0f1805e-12b2-11ea-8c10-00155d20546f

ECK works fine with my Docker for Windows with K8s.

Thx Peter

My Setup was

Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.8", GitCommit:"211047e9a1922595eaa3a1127ed365e9299a6c23", GitTreeState:"clean", BuildDate:"2019-10-15T12:11:03Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.8", GitCommit:"211047e9a1922595eaa3a1127ed365e9299a6c23", GitTreeState:"clean", BuildDate:"2019-10-15T12:02:12Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}

Client: Docker Engine - Community
 Version:           19.03.5
 API version:       1.40
 Go version:        go1.12.12
 Git commit:        633a0ea
 Built:             Wed Nov 13 07:22:37 2019
 OS/Arch:           windows/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.5
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.12
  Git commit:       633a0ea
  Built:            Wed Nov 13 07:29:19 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.2.10
  GitCommit:        b34a5c8af56e510852c35414db4c1f4fa6172339
 runc:
  Version:          1.0.0-rc8+dev
  GitCommit:        3e425f80a8c931f88e6d94a8c831b9d5aa481657
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683