Aleksandar Ivanov

Hm, I am hitting the same error, even though I am using Minikube or Kubeadm. Any suggestions?

Yes, it is deployed with helm chart and I did try both 0.6.4 and 0.6.3, but I get the same error. I thought that the issue is related with web/api...

@aalemanq So, the config `cat /etc/cerebro/application.conf` should look something like this: ``` ...... hosts = [ { host = "https://xxxx.europe-west4.gcp.elastic-cloud.com:xxxx" name = "cluster-name" auth = { username = "cerebro" password...

So, as many people pointed out the impact on user experience, this can be a deal breaker for those that are just starting out. This issue becomes even more exaggerated...

> Won't KCC eventually have this problem as well? @negz Not really, because KCC is a dedicated tool for doing one thing only, and that is managing gcloud, while Crossplane...

This does not have to be a direct implementation, but a separate opt-in component that and does translations for kubernetes API objects to the nanocl API objects.