Failed to get API Group-Resources

Hello World!

I'm trying to Deploy ECK in your Kubernetes cluster, yet running into following issue:

$ microk8s.kubectl apply -f https://download.elastic.co/downloads/eck/1.0.0-beta1/all-in-one.yaml
customresourcedefinition.apiextensions.k8s.io/apmservers.apm.k8s.elastic.co created
customresourcedefinition.apiextensions.k8s.io/elasticsearches.elasticsearch.k8s.elastic.co created
customresourcedefinition.apiextensions.k8s.io/kibanas.kibana.k8s.elastic.co created
clusterrole.rbac.authorization.k8s.io/elastic-operator created
clusterrolebinding.rbac.authorization.k8s.io/elastic-operator created
namespace/elastic-system created
statefulset.apps/elastic-operator created
serviceaccount/elastic-operator created
$ microk8s.kubectl -n elastic-system logs -f statefulset.apps/elastic-operator
Error from server: Get https://noc.uftwf.local:10250/containerLogs/elastic-system/elastic-operator-0/manager?follow=true: dial tcp: lookup noc.uftwf.local on 208.67.222.222:53: no such host
$ 

I thought maybe this would help:

$ echo "X.X.X.X	noc.uftwf.local" >> /etc/hosts
$ microk8s.kubectl -n elastic-system logs -f statefulset.apps/elastic-operator 
{"level":"info","@timestamp":"2019-11-04T21:30:03.518Z","logger":"manager","message":"Setting up client for manager","ver":"1.0.0-beta1-84792e30"}
{"level":"info","@timestamp":"2019-11-04T21:30:03.518Z","logger":"manager","message":"Setting up scheme","ver":"1.0.0-beta1-84792e30"}
{"level":"info","@timestamp":"2019-11-04T21:30:03.518Z","logger":"manager","message":"Setting up manager","ver":"1.0.0-beta1-84792e30"}
{"level":"error","@timestamp":"2019-11-04T21:30:04.563Z","logger":"controller-runtime.manager","message":"Failed to get API Group-Resources","ver":"1.0.0-beta1-84792e30","error":"Get https://10.152.183.1:443/api?timeout=32s: dial tcp 10.152.183.1:443: connect: no route to host","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128\nsigs.k8s.io/controller-runtime/pkg/manager.New\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.2.1/pkg/manager/manager.go:212\ngithub.com/elastic/cloud-on-k8s/cmd/manager.execute\n\t/go/src/github.com/elastic/cloud-on-k8s/cmd/manager/main.go:227\ngithub.com/elastic/cloud-on-k8s/cmd/manager.glob..func1\n\t/go/src/github.com/elastic/cloud-on-k8s/cmd/manager/main.go:74\ngithub.com/spf13/cobra.(*Command).execute\n\t/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:830\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\t/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:914\ngithub.com/spf13/cobra.(*Command).Execute\n\t/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:864\nmain.main\n\t/go/src/github.com/elastic/cloud-on-k8s/cmd/main.go:27\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:203"}
{"level":"error","@timestamp":"2019-11-04T21:30:04.564Z","logger":"manager","message":"unable to create controller manager","ver":"1.0.0-beta1-84792e30","error":"Get https://10.152.183.1:443/api?timeout=32s: dial tcp 10.152.183.1:443: connect: no route to host","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128\ngithub.com/elastic/cloud-on-k8s/cmd/manager.execute\n\t/go/src/github.com/elastic/cloud-on-k8s/cmd/manager/main.go:229\ngithub.com/elastic/cloud-on-k8s/cmd/manager.glob..func1\n\t/go/src/github.com/elastic/cloud-on-k8s/cmd/manager/main.go:74\ngithub.com/spf13/cobra.(*Command).execute\n\t/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:830\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\t/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:914\ngithub.com/spf13/cobra.(*Command).Execute\n\t/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:864\nmain.main\n\t/go/src/github.com/elastic/cloud-on-k8s/cmd/main.go:27\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:203"}
$ 

but it didn't(

Please advise.

This is odd:

 dial tcp: lookup noc.uftwf.local on 208.67.222.222:53: no such host

You are trying to resolve noc.uftwf.local with OpenDNS, looks like there is a problem with your setup.

dial tcp 10.152.183.1:443: connect: no route to host"

Same here, assuming that 10.152.183.1 is "service/kubernetes" it sounds like a network (maybe NetworkPolicy one) issue not related to ECK.

Thank you for your comment/reply, I really do appreciate your trying to help me)

I'm tried to install ECK on following Kubernetes distros:

I suppose, I can also try on minikube, all above k8s distros were used out of the box though...