Container Service for Kubernetes:Use MSE Ingresses to access applications in ACK clusters

Method 1: Use a Kubernetes IngressClass resource (recommended)

Use this method for new services that access the MSE Ingress. Run one of the following commands based on your cluster's Kubernetes version.

Clusters running Kubernetes versions earlier than v1.19

cat << EOF | kubectl apply -f -
apiVersion: networking.k8s.io/v1beta1
kind: IngressClass
metadata:
  name: mse
spec:
  controller: mse.alibabacloud.com/ingress
  parameters:
    apiGroup: mse.alibabacloud.com       # API group of MseIngressConfig
    kind: MseIngressConfig               # Resource kind
    name: test                           # Name of the MseIngressConfig from Step 1
EOF

Clusters running Kubernetes v1.19 or later

cat << EOF | kubectl apply -f -
apiVersion: networking.k8s.io/v1
kind: IngressClass
metadata:
  name: mse
spec:
  controller: mse.alibabacloud.com/ingress
  parameters:
    apiGroup: mse.alibabacloud.com       # API group of MseIngressConfig
    kind: MseIngressConfig               # Resource kind
    name: test                           # Name of the MseIngressConfig from Step 1
EOF

Method 2: Use MseIngressConfig resources (for migration)

Use this method when migrating from NGINX Ingress to MSE Ingress, or in scenarios where IngressClass resources cannot be created. During migration, both NGINX Ingress and MSE Ingress must listen to the same IngressClass resource. This method lets you configure the IngressClass directly within the MseIngressConfig, avoiding IngressClass name conflicts.

Add the ingressClass field to the MseIngressConfig created in Step 1:

apiVersion: mse.alibabacloud.com/v1alpha1
kind: MseIngressConfig
metadata:
  name: test
spec:
  name: mse-ingress
  common:
    instance:
      spec: 2c4g
      replicas: 3
  ingress:
    local:
      ingressClass: mse                  # IngressClass name to listen on

The following table describes the ingress.local.ingressClass values.

Verify the gateway status

Run the following command to check the MseIngressConfig status:

kubectl get MseIngressConfig test

Expected output:

NAME   STATUS      AGE
test   Listening   3m15s

The Listening status confirms that the cloud-native gateway is running and watching for Ingress resources associated with the mse IngressClass.

The status transitions in the following order:

Deploy a sample backend service

Run the following command to deploy the go-httpbin service:

cat << EOF | kubectl apply -f -
apiVersion: apps/v1
kind: Deployment
metadata:
  name: go-httpbin
  namespace: default
spec:
  replicas: 1
  selector:
    matchLabels:
      app: go-httpbin
  template:
    metadata:
      labels:
        app: go-httpbin
        version: v1
    spec:
      containers:
        - image: specialyang/go-httpbin:v3
          args:
            - "--port=8090"            # Application listens on port 8090
            - "--version=v1"           # Reports version v1
          imagePullPolicy: Always
          name: go-httpbin
          ports:
            - containerPort: 8090
---
apiVersion: v1
kind: Service
metadata:
  name: go-httpbin
  namespace: default
spec:
  ports:
    - port: 80                         # Service port exposed to Ingress
      targetPort: 8090                 # Forwards to container port 8090
      protocol: TCP
  selector:
    app: go-httpbin
EOF

Create an Ingress resource

Run one of the following commands to create an Ingress resource. The Ingress routes requests for example.com/version to the go-httpbin service.

cat << EOF | kubectl apply -f -
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: ingress
  namespace: default
spec:
  ingressClassName: mse                  # Associates with the MSE IngressClass
  rules:
   - host: example.com
     http:
      paths:
      - path: /version
        backend:
          serviceName: go-httpbin
          servicePort: 80
EOF

cat << EOF | kubectl apply -f -
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: ingress
  namespace: default
spec:
  ingressClassName: mse                  # Associates with the MSE IngressClass
  rules:
  - host: example.com
    http:
      paths:
      - backend:
          service:
            name: go-httpbin
            port:
              number: 80
        path: /version
        pathType: Prefix
EOF

Verify the result

1. Get the address assigned to the Ingress: Expected output:

      kubectl get ingress ingress

      NAME      CLASS   HOSTS            ADDRESS         PORTS   AGE
      ingress   mse     example.com      114.55.XX.XX   80      12m

2. Send a test request using the Ingress address: Expected output: The version:v1 response confirms that traffic is routed through the MSE Ingress to the go-httpbin backend service.

      curl -H "host: example.com" <ADDRESS>/version

      version:v1