Container Compute Service:Get started with ALB Ingresses

On the Clusters page, find the cluster that you want to manage and click its ID. In the left-side pane, choose Workloads > Deployments.

On the Deployments page, click Create from YAML in the upper-right corner.

Go to the Create page.

1. Sample Template: Select Custom from the drop-down list.

2. Template: Copy and paste the following code to the code editor. The YAML configuration file is used to deploy two Deployments named coffee and tea, and two Services named coffee-svc and tea-svc.

   YAML configuration file

   apiVersion: apps/v1
   kind: Deployment
   metadata:
     name: coffee
   spec:
     replicas: 2
     selector:
       matchLabels:
         app: coffee
     template:
       metadata:
         labels:
           app: coffee
       spec:
         containers:
         - name: coffee
           image: registry.cn-hangzhou.aliyuncs.com/acs-sample/nginxdemos:latest
           ports:
           - containerPort: 80
   ---
   apiVersion: v1
   kind: Service
   metadata:
     name: coffee-svc
   spec:
     ports:
     - port: 80
       targetPort: 80
       protocol: TCP
     selector:
       app: coffee
     type: ClusterIP
   ---
   apiVersion: apps/v1
   kind: Deployment
   metadata:
     name: tea
   spec:
     replicas: 2
     selector:
       matchLabels:
         app: tea
     template:
       metadata:
         labels:
           app: tea
       spec:
         containers:
         - name: tea
           image: registry.cn-hangzhou.aliyuncs.com/acs-sample/nginxdemos:latest
           ports:
           - containerPort: 80
   ---
   apiVersion: v1
   kind: Service
   metadata:
     name: tea-svc
   spec:
     ports:
     - port: 80
       targetPort: 80
       protocol: TCP
     selector:
       app: tea
     type: ClusterIP

After the configurations are complete, click Create. The Created message appears.

Verify that the Deployments and Services are created.

1. In the left-side navigation pane, choose Workloads > Deployments. The Deployments named coffee and tea are displayed.

2. In the left-side navigation pane, choose Network > Services. The Services named coffee-svc and tea-svc are displayed.

Create a file named cafe-service.yaml. Copy and paste the following content to the file. The file is used to deploy two Deployments named coffee and tea and two Services named coffee-svc and tea-svc.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: coffee
spec:
  replicas: 2
  selector:
    matchLabels:
      app: coffee
  template:
    metadata:
      labels:
        app: coffee
    spec:
      containers:
      - name: coffee
        image: registry.cn-hangzhou.aliyuncs.com/acs-sample/nginxdemos:latest
        ports:
        - containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: coffee-svc
spec:
  ports:
  - port: 80
    targetPort: 80
    protocol: TCP
  selector:
    app: coffee
  type: NodePort
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: tea
spec:
  replicas: 2
  selector:
    matchLabels:
      app: tea
  template:
    metadata:
      labels:
        app: tea
    spec:
      containers:
      - name: tea
        image: registry.cn-hangzhou.aliyuncs.com/acs-sample/nginxdemos:latest
        ports:
        - containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: tea-svc
spec:
  ports:
  - port: 80
    targetPort: 80
    protocol: TCP
  selector:
    app: tea
  type: NodePort

On the Clusters page, find the cluster that you want to manage and click its ID. In the left-side navigation pane, choose Workloads > Custom Resources.

Click Create from YAML in the upper-right corner.

1. Sample Template: Select Custom from the drop-down list.

2. Template: Copy and paste the following code to the code editor.

   YAML configuration file

   apiVersion: alibabacloud.com/v1
   kind: AlbConfig
   metadata:
     name: alb-demo
   spec:
     config:
       name: alb-test
       addressType: Internet
       zoneMappings:
       - vSwitchId: vsw-uf6ccg2a9g71hx8go**** # The vSwitch ID. Configure this parameter based on your business requirements.
       - vSwitchId: vsw-uf6nun9tql5t8nh15**** # The vSwitch ID. Configure this parameter based on your business requirements.
     listeners:
       - port: 80
         protocol: HTTP

   The following table describes the parameters that you can configure.

   Parameter	Required	Description
   metadata.name	Yes	The name of the AlbConfig. Note The name of the AlbConfig must be unique in the cluster. Therefore, when you create an AlbConfig, make sure that the AlbConfig name is unique to prevent name conflicts.
   spec.config.name	No	The name of the ALB instance.
   spec.config.addressType	No	The network type of the ALB instance. Valid values: Internet (default): Internet-facing. An Internet-facing ALB instance provides services to the Internet and is accessible over the Internet. Note To allow an ALB instance to provide Internet-facing services, the ALB instance needs to be associated with an elastic IP address (EIP). If you use an Internet-facing ALB instance, you are charged instance fees and bandwidth or data transfer fees for EIPs. For more information, see Pay-as-you-go. Intranet: internal-facing. An internal-facing ALB instance provides services within a VPC and cannot be accessed over the Internet.
   spec.config.zoneMappings	Yes	The ID of the vSwitch that is associated with the ALB instance. For more information about how to create a vSwitch, see Create and manage a vSwitch. Note The specified vSwitch must be deployed in a zone supported by the ALB instance and deployed in the same VPC as the cluster. For more information about the regions and zones supported by ALB, see Regions and zones supported by ALB. ALB supports multi-zone deployment. If the current region supports two or more zones, select vSwitches in at least two zones to ensure high availability.
   spec.listeners	No	The listener port and protocol of the ALB instance. In this example, an HTTP listener that uses port 80 is configured. A listener defines how ALB receives traffic. We recommend that you retain the listener configuration. Otherwise, you must create a listener before you can use ALB Ingresses.

After the configuration is complete, click Create. The Created message appears.

Verify that the ALB instance is created.

1. Log on to the ALB console.

2. In the top navigation bar, select the region in which the ALB instance is deployed.

3. On the Instances page, verify that the ALB instance named alb-test is displayed in the instance list.

Create a file named alb-test.yaml and add the following content to the file. The file is used to create an AlbConfig.

apiVersion: alibabacloud.com/v1
kind: AlbConfig
metadata:
  name: alb-demo
spec:
  config:
    name: alb-test
    addressType: Internet
    zoneMappings:
    - vSwitchId: vsw-uf6ccg2a9g71hx8go****
    - vSwitchId: vsw-uf6nun9tql5t8nh15****
  listeners:
    - port: 80
      protocol: HTTP

Run the following command to create an AlbConfig:

kubectl apply -f alb-test.yaml

albconfig.alibabacloud.com/alb-demo created

On the Clusters page, find the cluster that you want to manage and click its ID. In the left-side navigation pane, choose Workloads > Custom Resources.

Click Create from YAML in the upper-right corner.

1. Sample Template: Select Custom from the drop-down list.

2. Template: Copy and paste the following code to the code editor.

   YAML configuration file

   apiVersion: networking.k8s.io/v1
   kind: IngressClass
   metadata:
     name: alb
   spec:
     controller: ingress.k8s.alibabacloud/alb
     parameters:
       apiGroup: alibabacloud.com
       kind: AlbConfig
       name: alb-demo

   The following table describes the parameters that you can configure.

   Parameter	Required	Description
   metadata.name	Yes	The name of the IngressClass. Note The name of an IngressClass must be unique in the cluster. Therefore, when you create an IngressClass, make sure that the IngressClass name is unique to prevent name conflicts.
   spec.parameters.name	Yes	The name of the associated AlbConfig.

After the configuration is complete, click Create. The Created message appears.

Verify that the IngressClass is created.

1. In the left-side navigation pane, choose Workloads> Custom Resources.

2. Click the Resource Objects tab.

3. In the API Group search box, enter IngressClass. The IngressClass that you create is displayed.

Create a file named alb.yaml and add the following content to the file:

apiVersion: networking.k8s.io/v1
kind: IngressClass
metadata:
  name: alb
spec:
  controller: ingress.k8s.alibabacloud/alb
  parameters:
    apiGroup: alibabacloud.com
    kind: AlbConfig
    name: alb-demo

Run the following command to create an IngressClass:

  kubectl apply -f alb.yaml

ingressclass.networking.k8s.io/alb created

On the Clusters page, find the cluster that you want to manage and click its name. In the left-side navigation pane, choose Network > Ingresses.

On the Ingresses page, click Create Ingress. In the Create Ingress dialog box, configure the parameters.

After the configurations are complete, click OK in the lower-left corner of the Create Ingress panel.

Verify that the Ingress is created.

1. In the left-side navigation pane, choose Network > Ingresses. The Ingress named cafe-ingress is displayed.

2. In the Endpoint column of cafe-ingress, view the endpoint.

Create a file named cafe-ingress.yaml and add the following content to the file. The file is used to create an Ingress.

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: cafe-ingress 
spec:
  ingressClassName: alb
  rules:
   - host: demo.domain.ingress.top
     http:
      paths:
      # Specify a context path.
      - path: /tea
        pathType: ImplementationSpecific
        backend:
          service:
            name: tea-svc
            port:
              number: 80
      # Specify a context path.
      - path: /coffee
        pathType: ImplementationSpecific
        backend:
          service:
            name: coffee-svc
            port: 
              number: 80