We've identified a number of other small issues with the repo builder, and are rolling out more fixes. We've also added "plain dockerfile" support - in the situation where we cannot determine the language of a project, but there is a Dockerfile, we'll now just build that and deploy it :dancer:
Those fixes will launch within the next 30 minutes or so :)
Hello everyone! We've released a new Dynamic DNS service today - if you upgrade your KubeSail Agent, you should get a new domain with the suffix
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!
@/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!
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?
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.
If possible, could you share any details about the cluster (ie: how it was setup k3s, microk8s, rancher, etc)? Any details would be awesome
@/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.
Heya @flynmoose - Sorry for the delay - weve released a patch that should (try) to solve your issues. At very least you'll be able to delete the cluster from https://kubesail.com/clusters and try again. Let me know if you continue to run into any issues :heart:
Hello, mentions of shared cluster resources (for starter and teams accounts) seem to have been gone from pricing and documentation pages (I was not able to find today). It still works on my team with original allocation from before, but wondering if this is indication that this feature will slowly be phasing out for you to focus on other features? Asking because want to see if will need to account for shared cluster migration medium term. Thanks!
Hey @asarturas - unfortunately yes - we're starting to phase out the shared hosting. We do offer dedicated clusters, and we'd be happy to help you migrate! Hopefully you received an email about this (ill double check you're on the right email lists!). Feel free to reach out to us at support@kubesail.com and we can sort out a solution that works for you - we offer cluster setup and managed clusters which fit most use-cases just as well if not better than our shared tier offering. Let us know if we can help!!
@/all Hello everyone! We've released an update to our KubeSail agent that should resolve the very last of the situations where Domains will not be routed properly (Ingress detection). Please update your agent using the https://kubesail.com/clusters dashboard. We've also added some great new templates in the last few days - please recommend any open-source software you'd like to see in our Template store! Thanks everyone! Loads of news coming soon !
Also, if I was interested in running kubesail on my own private domain but without depending on an external website how would it be possible to deploy my cluster under my domain?
Thanks for your time and consideration
I'm a software engineering student currently teaching myself devops and kubernetes. I had some ideas for a few PaaS I wanted to self host and test deploy on my cluster of RPIs but i couldnt find any easy to use tools to manage my cluster asides from garden.io and kubesail. Would appreciate any advice any of you may have on how I could proceed. Thanks again.
@RyzeNGrind I use https://k8slens.dev/ to complement Kubesail, also works with Docker Desktop, k3s, should work with any k8s. Just copy-paste the kube config. It includes its own copy of kubect.
@RyzeNGrind - Technically, you can buy a domain, and point that domain at your home IP address, and as long as you tell your Kubernetes cluster about that domain, things should just work - in k3s the option is
--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 :)
Hello. Issues with letsencrypt certificates. On account jflamy I created a BYOC cluster. I deleted the existing ingresses and secrets, and used the KubeSail interface to reinstall nginx and the cert manager. I then recreated the ingresses. Because that account is a free account, I get https://owlcms.owlcms.jflamy.usw1.k8g8.com and https://results.owlcms.jflamy.usw1.k8g8.com but both fail as they still publish a self-signed certificate.
@erulabs see just above for issues on letsencrypt for BYOC. Maybe am just impatient?
Ack! It looks like when you accept the invalid certificate at https://owlcms.owlcms.jflamy.usw1.k8g8.com/ it says 'No ingress controller found!' - that message comes from the KubeSail agent - so at least the gateway <-> agent connection is working properly - but the agent wasn't able to find your ingress controller.
It should find it pretty quickly - I wonder if you checked the logs in the
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.
The ingress needs to work first before the certificates are able to generate (the cert-manager uses the ingress system for validation with LetsEncrypt)
If restarting the agent does the trick, would you mind sharing what version of the agent you're using (should be in the logs and on the kubesail dashboard at https://kubesail.com/clusters and then click 'Details')
I just recently modified the code that searches for ingress controllers, and some people have reported issues - it's possible there is still one lurking :(
Ah, I see
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:
Ideally, the certificate should go valid shortly (you can check the
cert-manager pod in that namespace and the logs should say what's happening - I plan on surfacing this in the UI much better in the future)
Works indeed. The dropdown does not read the current setting, which is slightly misleading.
I'll investigate both of those bugs asap :heart:
That cluster had my custom domain ingress file referencing letsencrypt certificates (but no certmanager) and an existing nginx. I bushwacked my way by asking kubesail to do the nginx and cert-manager installs, deleting the two existing ingresses, and recreating repeatedly. After restart of the agent, there may be hidden stuff left, but I don't see any using Lens or the web interface.
@jflamy We've recently released a lot of updates to the KubeSail agent - so I do recommend if you go to https://kubesail.com/clusters you should be able to upgrade your agent in the 'Details' page - hopefully that resolves the problem with the agent discovering the ingress controller. It's still possible that's not 100% perfect tho, but a restart of the agent usually does the trick (if the ingress system changes a lot). You might also check the
/resources tab 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!
@erulabs thank you for breaking it down and elaborating. Would I be able to use a dynamic DNS to self manage the cluster? I have openwrt with ddns client on my home router.
@erulabs given the magnitude of the ingress changes (new names and new secrets) and my brutal way of updating (delete and recreate) it's not really surprising that a restart was needed
Hehe - yes, I'm not surprised either, but our agent code listens to changes to the ingress system and should react properly - that might have been a little more than it can handle but either way I'd like it to handle it eventually - can be non-obvious that it just needs a restart to pick up the changes. Glad you got it sorted though! Going to add a test for that situation to my list either way <3