You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, porter ships with service types for the Web, Workers, and CronJobs. Applications that don't run on the web don't fit any of these categories, such as apps like Minecraft servers (and game servers in general). Although my use case is for a custom provisioned kube cluster, this could be applied to the cloud as well, to provision load balancers automatically for applications that don't utilize HTTP(s) and can't use Ingresses.
Requirements
Porter should ship with an additional Application service type, which should be similar to how https://railway.app/ does it, which allows for a port to be forwarded to a TCP proxy (LoadBalancer in Kube). I'm not sure if any cloud load balancers on kubernetes supports sharing ports, but MetalLB does, and the solution could include support for that or something similar to have the ports all from one LoadBalancer service. However, most clusters would use one LoadBalancer for each service, and this should be primarily supported as well.
The text was updated successfully, but these errors were encountered:
Location
Motivation
Currently, porter ships with service types for the Web, Workers, and CronJobs. Applications that don't run on the web don't fit any of these categories, such as apps like Minecraft servers (and game servers in general). Although my use case is for a custom provisioned kube cluster, this could be applied to the cloud as well, to provision load balancers automatically for applications that don't utilize HTTP(s) and can't use Ingresses.
Requirements
Porter should ship with an additional Application service type, which should be similar to how https://railway.app/ does it, which allows for a port to be forwarded to a TCP proxy (LoadBalancer in Kube). I'm not sure if any cloud load balancers on kubernetes supports sharing ports, but MetalLB does, and the solution could include support for that or something similar to have the ports all from one LoadBalancer service. However, most clusters would use one LoadBalancer for each service, and this should be primarily supported as well.
The text was updated successfully, but these errors were encountered: