Container Service for Kubernetes:Deploy the AI suite console in an ACK Edge cluster

Prerequisites

• An ACK Edge cluster that runs Kubernetes 1.18 or later is available. For more information, see Create a cluster.

• The csi-plugin and csi-provisioner components are installed in the edge cluster. For more information, see Manage components.

Step 1: Deploy the Nginx Ingress controller

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

2. On the Clusters page, click the name of your cluster. In the left navigation pane, click Applications > Helm.

3. On the Helm page, click Deploy. Configure the Basic Information parameters.

   Parameter	Value
   Application Name	ack-ingress-nginx-{node-pool-name}
   Namespace	kube-system
   Source	The default value is Marketplace.
   Chart	Use Scenarios: Select All. Supported Architecture: Select amd64. Search box: Search for ack-ingress-nginx-v1.

4. Click Next. On the Parameters page, configure the parameters and click OK.

   Note

   To find the ID of the cloud-side node pool, log on to the ACK console. In the navigation pane on the left, choose Nodes > Node Pools to view the list of node pools.

   • In the nodeSelector parameter, add the cloud node pool label: alibabacloud.com/nodepool-id: {node-pool-id}.

     Note

     In the nodeSelector field, keep only alibabacloud.com/nodepool-id: {node-pool-id}.

     

   • In the ingressClassResource parameter, set name and controllerValue.

     Note

     If you deploy ack-ingress-nginx-v1 multiple times in the same ACK Edge cluster, ensure that the name and controllerValue are unique for each deployment. Recommended naming conventions:

     • name: ack-nginx-{node-pool-name}. For example: ack-nginx-edge-hangzhou.

     • controllerValue: "k8s.io/ack-ingress-nginx-{node-pool-name}". For example: "k8s.io/ack-ingress-nginx-edge-hangzhou".

     

   • On the Parameters page, select a Server Load Balancer (SLB) type (public or private) based on your requirements, and set the enabled values under external and internal accordingly. If you choose an SLB on the public network, resolve your domain name to the public IP address. If you choose an SLB on the private network, use an accessible and resolvable private IP address.

     service:
         # enable public or private network SLB
         enabled: true
         external:
         # enable public network SLB
           enabled: true
         # public network SLB annotations
         # NOTE: if you want to remove default annotations below, please set it to null.
         annotations:
           service.beta.kubernetes.io/alibaba-cloud-loadbalancer-address-type: "internet"
         ## Enables an additional internal load balancer (besides the external one).
         ## Annotations are mandatory for the load balancer to come up. Varies with the cloud service.
         internal:
           # enable private network SLB
           enabled: false
         # private network SLB annotations
         # NOTE: if you want to remove default annotations below, please set it to null.
         annotations:
           service.beta.kubernetes.io/alibaba-cloud-loadbalancer-address-type: "intranet"

Step 2: Deploy the AI suite console

For detailed instructions, see Deploy the cloud-native AI suite. Note the following points during the installation.

• We recommend that you deploy the AI suite console components on cloud-side nodes to fully use cloud capabilities. If you want to schedule the components to a specific node pool, set the Selector or Affinity for the corresponding component pods.

• If you use a self-managed data store in your cluster, you must select and install the ack-mysql component when you deploy the AI suite console. This component must be deployed on a cloud-side node.

  After the installation is complete, two ingress entries for the consoles are added to the Ingresses page. You must add an ingressClassName configuration to specify that the ingress entries use the same IngressClass as the deployed Nginx Ingress.

  1. In the navigation pane on the left, choose Network > Ingresses. For each of the two ingress entries, click Edit YAML in the Actions column.

  2. Add the ingressClassName configuration and ensure that its value matches the ingressClassResource.name from Step 1. Change the ingressClassName field to ack-nginx-edge-hangzhou. The following YAML code provides an example:

     spec:
       ingressClassName: ack-nginx-edge-hangzhou
       rules:
         - host: asdfgasdfasfdasdfasdfasd
           http:
             paths:
               - backend:
                   service:
                     name: ack-ai-dashboard-admin-ui
                     port:
                       number: 80
                 path: /
                 pathType: Prefix

• During the deployment, if you need to access the console by using a public domain name, you must resolve the domain name to the IP address of the Nginx Ingress load balancer. To find this IP address, choose Network > Services in the navigation pane on the left. In the service list, find the service related to ack-ingress-nginx of the LoadBalancer type and view the public IP address in the External IP column.

After the deployment is complete, you can access the AI Dashboard. For more information, see Access AI Dashboard.