So it seems to be working ok. The ingress is created and the TLS certificate is finalized and the k8g8.com URL works. But there doesn't seem to be any logging now. At least not like before. With 0.19.0 when a new ingress is created the agent would log and new firewall listing with the new host added. Also when the agent was restarted it would log the current firewall list of hosts. but now just:
(2021-01-12T22:11:44.529Z) info: kubesail-agent starting! { "version": "0.22.0" }
(2021-01-12T22:11:46.403Z) info: KubeSail Agent registered and ready! KubeSail support information: {
"clusterAddress": "n40x7k8s.dklinkman.usw1.k8g8.com",
"agentKey": "6e69954ddcd8d642be27b08405e2aabd",
"version": "0.22.0"
}
Functionally it seems to be working fine, just the logging looks different
kubectl create...
). Let me know if you have any questions!
dns.k8g8.com
- this is a dynamic DNS address that will point at your machines public IP address! Very useful for hosting games, SSH servers, and anything non-http that the Gateway tunneling service doesn't address for you. Let me know if you have any questions! Thanks everyone!
1000 monkeys and 1000 typewriters... Didn't really know (nor still know) what I was doing when I tried to connect my RPi to KubeSail and ended up with some persistent errors that I am trying to get rid of so I can start over. Any idea how to clear these red warning boxes every time I log in?
Permission denied from Games
games.xxxxxx.usw1.k8g8.com / Deployment Invalid clusterConfig from db - no credentials found for cluster: games.xxxxxx.usw1.k8g8.com
Unable to fetch namespaces from games.xxxxxx.usw1.k8g8.com
games.xxxxxx.usw1.k8g8.com might be offline?
@/all New features this week! Dynamic DNS, plain-Dockerfile support in Repo-Builder, lots of improvements and bug-fixes around the site, and lots more coming soon! Also excited to announce the launch of https://www.beeperhq.com - a customer of ours built on KubeSail's platform. Thanks everyone and have a great week!
Wow Beeper looks amazing and can't believe its self hosted on a cluster somewhere. Super cool thanks for sharing this gem!
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-address
for 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-agent
namespace, 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.