Using ksync with micro8ks

[KASOGIT]

Hello,

i would like to know if there is a way to use ksync with microk8s with a local setup ?

Following ksync' tutorial doesn't seems to work..

Thx !

[grampelberg]

What's not working? Anything in the logs? What's the output of doctor? What's the output of microk8s.inspect?

[KASOGIT]

Hi @grampelberg ! microk8s.inspect:

Inspecting services
  Service snap.microk8s.daemon-docker is running
  Service snap.microk8s.daemon-apiserver is running
  Service snap.microk8s.daemon-proxy is running
  Service snap.microk8s.daemon-kubelet is running
  Service snap.microk8s.daemon-scheduler is running
  Service snap.microk8s.daemon-controller-manager is running
  Service snap.microk8s.daemon-etcd is running
  Copy service arguments to the final report tarball
Inspecting AppArmor configuration
Gathering system info
  Copy network configuration to the final report tarball
  Copy processes list to the final report tarball
  Copy snap list to the final report tarball
  Inspect kubernetes cluster

ksync doctor:

Extra Binaries                              ✓
Cluster Config                              ✓
Cluster Connection                          ✘
↳	Unable to contact the cluster for context (). Does 'kubectl --context= cluster-info' work?

ksync watch:

FATA[0000] Get https://192.168.99.100:8443/api/v1/namespaces/default/pods?watch=true: dial tcp 192.168.99.100:8443: connect: no route to host

kubectl cluster-info:

microk8s.kubectl cluster-info
Kubernetes master is running at http://127.0.0.1:8080
Heapster is running at http://127.0.0.1:8080/api/v1/namespaces/kube-system/services/heapster/proxy
KubeDNS is running at http://127.0.0.1:8080/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
Grafana is running at http://127.0.0.1:8080/api/v1/namespaces/kube-system/services/monitoring-grafana/proxy
InfluxDB is running at http://127.0.0.1:8080/api/v1/namespaces/kube-system/services/monitoring-influxdb:http/proxy

[timfallmk]

@KASOGIT Can you (safely) post your kubeconfig?

[timfallmk]

Closing for lack of updates. Please reopen if necessary.

[johnbendi]

Hello, I'm using microk8s.

When I try to run ksync init
I get the following error message FATA[0000] Unable to get config for context (). Does 'kubectl --context= cluster-info' work?

When I run kubectl --context= cluster-info
I get

Kubernetes control plane is running at https://127.0.0.1:16443
CoreDNS is running at https://127.0.0.1:16443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
Metrics-server is running at https://127.0.0.1:16443/api/v1/namespaces/kube-system/services/https:metrics-server:/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'

My kubectl version

Client Version: version.Info{Major:"1", Minor:"20+", GitVersion:"v1.20.9-34+90ae618987e17a", GitCommit:"90ae618987e17a41856095693df31a22ea81c9f9", GitTreeState:"clean", BuildDate:"2021-08-01T06:03:53Z", GoVersion:"go1.15.14", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"20+", GitVersion:"v1.20.9-34+90ae618987e17a", GitCommit:"90ae618987e17a41856095693df31a22ea81c9f9", GitTreeState:"clean", BuildDate:"2021-08-01T06:04:56Z", GoVersion:"go1.15.14", Compiler:"gc", Platform:"linux/amd64"}