Seems every time I try to deploy “Private service” , select Github, it auto-reverts to “Web service” on next screens like service summary - without a way to change it to Private service". It only lists “Web service” and “Worker”.
What you’re seeing is correct, Koyeb doesn’t currently provide support for workers on the free tier. If you need to run a background worker, you’ll need to either upgrade to a paid plan or look into alternative services that support free-tier workers.
Keep in mind that pricing and free tier terms can change, so it’s good to check the new prices every now and then.
Hello,
Sorry to clarify - my question was more on private vs web endpoint, it seems the UI force changes to web endpoint and doesn’t take private setting
Ah, I see what you mean now.
Yes, even though the UI shows “Web Service” in the settings, if you initially selected “Private Service”, it will be deployed as a private instance.
As long as you selected “Private” at the start, your service won’t have a public endpoint, only an internal one, which is (as far as I know) like a private service should.
Hi,
As long as you selected “Private” at the start, your service won’t have a public endpoint
That’s correct. A “private service” is actually a web service with a port that is not exposed publicly (it’s only exposed within the service mesh).
Yes, but why is this option still here? Do workers feature something different than not being exposed to the internet as well? Else this option could be removed when creating a private service.
Workers are different from private services, as they do not expose ports (they cannot handle incoming connection). Here’s the documentation for more information.
“Private services” don’t really exist, but as users were looking for a way to create a service that is not exposed to the internet, we introduced this entry in the service creation flow.
1 Like