All Products
Search

This Product

    Enterprise Distributed Application Service:Access CNKIT

    Document Center

    Enterprise Distributed Application Service:Access CNKIT

    Last Updated:Jun 28, 2023

    This topic describes how to access Cloud Native Kit (CNKIT) after you install it.

    Background information

    After you install CNKIT, you can go to the CNKIT page by using three methods. The following figure shows the methods.

    访问云原生工具箱

    Method 1: Use an NGINX Ingress to access CNKIT

    By default, an NGINX Ingress is provided as an access point for external requests to access CNKIT after you install CNKIT.

    1. If you want to use an NGINX Ingress to access CNKIT, make sure that the NGINX Ingress controller is installed in your Container Service for Kubernetes (ACK) cluster. For more information, see Install the NGINX Ingress controller. To check whether the NGINX Ingress controller is installed, perform the following operations:

      1. Log on to the ACK console. In the left-side navigation pane, click Clusters.

      2. On the Clusters page, find the cluster that you want to manage and choose More > Manage Components in the Actions column.

      3. On the Add-ons page, click the Networking tab to check whether the NGINX Ingress controller is installed.

    2. By default, an Ingress that points to CNKIT is added when you install CNKIT.

    3. After you install CNKIT, refresh the page. If Ready appears on the right of Ingress, click One-click Access to access and use CNKIT.

    Note

    • By default, an NGINX Ingress is added to an Internet-facing Server Load Balancer (SLB) instance for a cluster that is created in ACK. This exposes the services in the cluster to external access requests. You can add the NGINX Ingress to an internal-facing SLB instance. This blocks access requests that are sent to CNKIT by using an Ingress over the Internet.

    • Changes on the Nginx Ingress controller may cause exceptions when you access CNKIT by using the NGINX Ingress. If access exceptions occur, perform the following operations to rebind a test domain name. After you complete the operation, wait 10 minutes and try to access CNKIT again.

      1. Log on to the ACK console.

      2. In the left-side navigation pane, click Clusters. On the Clusters page, find the cluster that you want to manage and click Details in the Actions column.

      3. On the Basic Information tab of the application details page, click Rebind Domain Name on the right of the value of the Testing Domain parameter in the Cluster Information section.

    Method 2: Use Internet-facing SLB to access CNKIT

    You can configure Internet-facing SLB to access CNKIT.

    1. From the Select SLB drop-down list, select an existing SLB instance. You can also create an SLB instance.

    2. After you select the SLB instance, add an HTTP or HTTPS listener.

      Note

      The value of the Container Port (Target Port) parameter for the listener is autopopulated as 8090 and cannot be changed.

      • If you want to add an HTTP listener, specify an external access port and add an access control list (ACL) whitelist.

      • If you want to add an HTTPS listener, specify an external access port, add an ACL whitelist, and then select an SSL certificate.

    3. After you add a listener, click OK. Then, click One-click Access to access CNKIT.

    负载均衡访问

    Method 3: Use the CNKIT agent to access CNKIT from an on-premises machine

    You can use the CNKIT agent to access CNKIT from your on-premises machine. Use one of the following methods:

    The CNKIT agent is provided in the following distributions: the CNKIT agent for Windows and the CNKIT agent for macOS. This section describes how to run the CNKIT agent to access CNKIT from your on-premises machine. In this example, the CNKIT agent for macOS is used.

    1. Save the Kubeconfig file of the Kubernetes cluster in which your application is deployed to your on-premises machine. You can find the Kubeconfig file on the Connection Information tab of the cluster in the ACK console. For more information, see View connection information.

    2. Download the CNKIT agent for macOS. You can download the agent only from the CNKIT module on the application details page in the EDAS console.

    3. Switch to the path of the downloaded file on your on-premises machine and run the following commands. The path varies based on the download settings of your browser. 

      # Switch to the path of the downloaded file.
➜  ~ cd Downloads
# Grant the permissions that are required to run the agent.
➜  Downloads sudo chmod +x ./cnkit
# Run the agent. The agent may be blocked by the system.
➜  Downloads ./cnkit proxy --kubeconfig=<Path of the Kubeconfig file of your cluster>
[1]    72186 killed     ./cnkit proxy --kubeconfig=<Path of the Kubeconfig file of your cluster>

    4. Click Cancel in the message that indicates CNKIT cannot be opened because the developer cannot be verified. This message may appear due to the security settings of your system.

    5. Unblock the CNKIT agent in the system. To do this, open the system settings on your on-premises machine and choose Security and Privacy > Allow.

    6. Run the CNKIT agent on your on-premises machine again. 

      # Run the CNKIT agent. 
➜  Downloads ./cnkit proxy --kubeconfig=<Path of the Kubeconfig file of your cluster>
select pod: cnkit-78b9dbd88d-w7r72 as port-forward endpoint.
Forwarding from [::1]:8090 -> 8090
proxy successfully, you can visit by http://127.0.0.1:8090/

    7. Click Open in the message that prompts you to confirm whether to open CNKIT.

    8. Click One-click Access when the proxy successfully message appears on your on-premises machine.

      一键访问