Hey @flynmoose ! Thanks for reaching out - I sent you an email about that error - we're trying to nail it down and eliminate it but its a hard one to recreate! If you go to https://kubesail.com/clusters and click "Settings", you should be able to delete the cluster from the dashboard entirely. Once that's done, you can try re-installing the agent (add-cluster), and it should do the trick.
Emailed you back with some screenshots and a commandline history of my buffonery. Hope it helps.
--advertise-addressfor example. But KubeSail does aim to make this easier by automatically assigning you an address for your cluster, and automatically setting a DNS name for your home-IP address. I hope this answers that question. There is no ETA for GitLab on the site just yet, but you can install the GitLab runner on your cluster yourself and things should work normally (just won't be on the KubeSail website). That's all a bit complex, so let me know if I misunderstood your question and I'd be happy to help :)
kubesail-agentnamespace, it might print that it couldn't find any ingress controller. You may try restarting the agent and seeing if the ingress starts to work.
https://owlcms.owlcms.jflamy.usw1.k8g8.com/returns an Nginx message now - so one step forward! I assume restarting the agent did the trick there... I'll look into that asap, that's not a good bug :crying_cat_face:
cert-managerpod in that namespace and the logs should say what's happening - I plan on surfacing this in the UI much better in the future)
/resourcestab which should show the raw ingress documents more clearly. I'd be happy to do a Zoom call as well if you need a hand getting things sorted out :) Thanks for keeping at it!
2021/01/28 17:11:32 http: proxy error: x509: certificate is valid for docker-for-desktop, kubernetes, kubernetes.default, kubernetes.default.svc, kubernetes.default.svc.cluster.local, kubernetes .docker.internal, vm.docker.internal, localhost, not owlcms.jflamy.usw1.k8g8.com
insecure-skip-tls-verify: trueto your KubeConfig and lens should respect that. The alternative option is to boot your kube cluster in such a way that it has
owlcms.jflamy.usw1.k8g8.comas its "advertise address" - the first option should be a lot easier to get going, but is a bit less secure
clusters: - cluster: server: your-address insecure-skip-tls-verify: true