Third-party Service Access
Enterprises build their own private clouds based on Kato. In the process of managing all the applications of the enterprise, they will encounter such a problem. Some applications need to be accessed by the public network, but due to various reasons, the applications have not yet been migrated to Kato. But the company only has one public IP. In order to enable applications inside and outside the Kato cluster to provide services to the Internet at the same time, users have to deploy a separate nginx service as the outermost application load. The problem brought about by this is that there is no way to directly and conveniently use the Kato gateway. Each open application requires manual configuration of nginx rules. If you do not understand the working principle of the Kato gateway, the process will be more complicated.
In order to solve this problem, combined with other requirements, Kato third-party component management integration function came into being. Refer to thirdparty service definition
This article will practice how to use third-party components, so that applications that have not been migrated to the Kato cluster can also be directly dynamically registered to the Kato gateway, so as to realize the management of all external service applications of the enterprise based on the Kato gateway.
Please make sure you have installed Kato V5.1 or higher.
Intranet? Other components, this article uses an Nginx application to illustrate.
Step 1: Fill in the Third-party Component Information
Log in to the Kato console, and go to
Create Application ->
Add Third-Party Components.
Fill in the information such as
component registration method (taking static registration as an example),
component address and other information.
Create Component, and after the test passes, click
Step 2: Add Port
After the creation is complete, you will enter the component management page. Select
Port in the navigation.
Add Port, enter the port as
80, and select the
After the addition is complete, open the
External Service and let the application gateway proxy the service.
It should be noted here that internal services can add multiple ports, while third-party services can only add one port.
Step 3: Confirm Service
After opening the
External Service, you will get a domain name similar to
http://80.grf53077.ex05o2yt.2cbcac.grapps.ca/, which Kato will assign a default domain name for the service. The most important thing is At this time, you can customize the domain name and set the required access policy parameters for the service in Gateway.
Reference document Gateway access policy management
If you need to set up Https certificate, please refer to the document Certificate Management
Enter the default domain name assigned by the platform in the browser to see if the component is running.
You should see a webpage similar to the following in your browser:
At this point, you have added
Nginx(192.168.1.123:80) as a third-party component to Kato, and successfully proxy the Nginx default page using the gateway.
Step 4: Overview Page
Overview in the navigation, you can see the information of the component instance, including the number of the instance, the address, the health status and the online status.
In addition to viewing the component instance information, you can also perform operations such as
Offline on the instance in the overview page.
Add, enter the instance address
When a new instance is added, the instance will be’online' by default.
As shown below:
The instance address cannot be a local loopback address such as 127.0.0.1
Next, take the newly added instance
192.168.1.200 offline. Select the instance
192.168.1.200, and click?
Then, you can see that the offline instance
192.168.1.200 will have no health status (displayed as'-'). As shown in the figure:
At this point, you should understand the basic usage of Kato V5.1’s new feature
third-party services; and understand the access to other components in the cluster through the gateway.