Also, in this whole process, I think I managed to pay for a month of the starter package twice. Is it possible to either cancel that second charge or have it applied to my account?
Going to upgrade your namespace shortly, but found an bug with our upgrader tool and am currently waiting for the patch to build heheh.
Thanks for using KubeSail by the way!
Let me know if I can do anything else to help and feel free to tell your friends! :D
@wasv That's actually going to be re-enabled hopefully today! It was being used a lot for abuse and malicious behavior so we temporarily disabled it while we worked on a few barriers for the attackers... It was a huge bummer to disable it and I really really wanted to avoid it. But due to your request I will prioritize bringing that back ASAP! I know I want to get my Factorio server running again!
(That said, existing TCP services where not taken down when the UI element was disabled)
Heya @wasv - External TCP services should now work, but the UI is still under development. In any case, you should be able to expose external services if you use a specific
externalIP in a NodePort service. Here is an example template: https://kubesail.com/template/erulabs/externalip-example/1 - which results in http://13.52.171.178:57219 being up and running. Consider this to be a beta, but you can go ahead and use that IP and you should get an automatically generated TCP port that you can point what whatever you'd like!
@erulabs I tried setting up my taskwarrior server using that IP, and the ones attached to my domain. I also tried setting up a TCP echo server from istio/samples/tcp-echo. I wasn't able to connect to any of these services using netcat. But I could connect to the tcp-echo service within the cluster from a busybox image.
It seems the new external IP might not be working properly. (also, if I shouldn't have (@)'ed, feel free to say so)
Sorry for bothering, looks like I was using too many resources and somehow messed creating services from UI/manifest, I've eventually managed to deploy and expose the ingress at https://frontend.recuencojones.usw1.kubesail.io ! Thanks anyways! :D
@RecuencoJones what you had prior to this commit (https://github.com/RecuencoJones/caddy-frontend/commit/a21fbebf40e13f46acb6e98b40515fda27cfbab5#diff-777f1d5227004ef17cf9b684feb83798R8-R17) actually would have worked, but we had a bug! We incorrectly mutated the incoming ingress request to add
frontend.recuencojones.kubesail.io instead of frontend.recuencojones.usw1.kubesail.io, but it looks like you figured that out before we fixed it :-D Sorry for the confusion that caused!
A fix for that is rolling out now, so future ingresses you create will work without adding an explicit host.
Still looking into the certificate issue
Hey @RecuencoJones https://frontend.recuencojones.usw1.kubesail.io/ should now have a proper certificate - sorry for the delay! A concurrency bug in our certificate issuing system bit us :( Thank you so much for the report! We're ready to call this issue resolved, but please let us know if you have any other issues, questions or comments! Thanks again!
You're awesome, thanks a lot for this!
Please feel free to reach out here if you have any questions or comments or feature requests - we've got big plans so stay tuned!
Hello everyone! We've been rolling out upgrades today - your containers may restart, and a small handful of customers on the
usw1 cluster might have seen a brief (~8 min) downtime. We're working on strategies to prevent this in the future - and obviously anyone with multiple replicas probably didn't see any downtime. Please let us know if you're having any troubles! Thanks!!
We're also taking signups / requests for our private beta of Deploy-from-Github - please reach out to me if you'd like to give it a shot!
We expect to make it generally available by next week :D
