Enterprise Distributed Application Service:Access Cloud Native Kit (CNKIT)

Prerequisites

Before you begin, make sure that:

• CNKIT is installed in your ACK cluster

• The NGINX Ingress controller is installed in the same cluster. For details, see Install the NGINX Ingress controller

To verify whether the NGINX Ingress controller is installed:

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

2. On the Clusters page, find the target cluster and choose More > Manage Components in the Actions column.

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

Procedure

1. After you install CNKIT, refresh the page.

2. When Ready appears next to Ingress, click One-click Access to open the CNKIT web UI.

Troubleshoot Ingress access exceptions

Changes to the NGINX Ingress controller can cause access failures. If CNKIT becomes unreachable through the Ingress, rebind the testing domain:

1. Log on to the ACK console.

2. In the left-side navigation pane, click Clusters. On the Clusters page, find the target cluster and click Details in the Actions column.

3. On the Basic Information tab, locate the Cluster Information section and click Rebind Domain Name next to the Testing Domain parameter.

4. Wait 10 minutes, then try accessing CNKIT again.

Procedure

1. From the Select SLB drop-down list, select an existing SLB instance or create a new one.

2. Add a listener to the selected SLB instance:

   • HTTP listener: Specify an external access port and add a whitelist through an access control list (ACL).

   • HTTPS listener: Specify an external access port, add a whitelist through an ACL, and select an SSL certificate.

   Note

   The Container Port (Target Port) is automatically set to 8090 and cannot be changed.

3. Click OK, then click One-click Access to open the CNKIT web UI.

Prerequisites

Before you begin, make sure that:

• CNKIT is installed in your ACK cluster

• The Kubeconfig file for your cluster is saved to your on-premises machine. Download it from the Connection Information tab of the cluster in the ACK console. For details, see View connection information

• The CNKIT agent binary is downloaded from the CNKIT module on the application details page in the EDAS console

Procedure

1. Open a terminal and navigate to the directory where the CNKIT agent binary is saved:

   cd ~/Downloads

2. Grant execute permission to the agent:

   sudo chmod +x ./cnkit

3. Start the agent proxy:

   ./cnkit proxy --kubeconfig=<path-to-kubeconfig>

   Replace <path-to-kubeconfig> with the absolute path to your cluster's Kubeconfig file.

4. When the following output appears, the proxy is running:

   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/

5. Click One-click Access in the EDAS console to open the CNKIT web UI.

Unblock the agent on macOS

On macOS, the system may block the CNKIT agent because the developer is not verified. To resolve this:

1. When the "developer cannot be verified" message appears, click Cancel.

2. Open System Settings and go to Security and Privacy.

3. Click Allow to unblock the CNKIT agent.

4. Run the agent again:

   ./cnkit proxy --kubeconfig=<path-to-kubeconfig>

5. When prompted to confirm, click Open.