spec icon indicating copy to clipboard operation
spec copied to clipboard

Define network gateway rule for application.

Open barnettZQG opened this issue 5 years ago • 1 comments

Most applications offer port services. If we just define the port mapping. Is the scalability here insufficient?

The application model we define will be deployed primarily on the cloud-native platform. How to access the application through the platform's external application gateway after deployment This is a model description. For example, an application that provides web services. Accessing it through a domain name is a common requirement. Here we describe the access rules of the application through the http protocol.

Here are some key attributes such as domain name, request path, request header, and cookies. It even includes upload limits, timeouts, and more. For a standard application model, perhaps only the domain name is specified when it is installed. Others may be standard needs, We need to define them in the application model. So the application should include gateway_rule in addition to the component.

barnettZQG avatar Nov 08 '19 06:11 barnettZQG

It seems what you said is a dozen of traits, including ingress trait, flow limit trait, etc..

Cloud you give some detail cases for gateway_rule adding into component that could benifit Application Developer?

wonderflow avatar Nov 09 '19 01:11 wonderflow