[Upcoming Feature] Port/Domain setup revamp Liveness/Readiness probes + new protocols

Hello there,

another upcoming cool feature here! But actually is more like a big refacto rather than a new feature itself.

We have decided to merge the Port and Custom Domains setup since they are strictly related one to the other.

As you can see in the image, you will have a single section to declare and manage the port of your application, see the associated domains and as well declare new custom domains.

At the same time, we will work on moving out the Liveness/Readiness probes setup from the advanced settings and make them 100% part of the product. They are often changed by our customers and thus it is the right time to let you configure them directly in the creation flow and within the service settings.

As you can see, you need to specify a port where you want to run the liveness and readiness probes, something that is not possible today (by default, we use the first one)

If you are new to Kubernetes probes and want to know more, have a look at this video.

And since we are working on this part, we will include some improvements:

  • More than one public port: you will be able to expose more than one public port for your application (for example the main port and an admin port). Today only 1 public port per application is authorized.
  • GRPC support: you will be able to expose your application via the GRPC protocol!