Container Compute Service:Configure certificates for encrypted communication over HTTPS

Choose a method

Use automatic discovery when your certificates are purchased or uploaded to Certificate Management Service and you want zero-touch binding based on domain names.

Use Kubernetes Secrets when you manage certificates inside the cluster, for example with cert-manager.

Use AlbConfig binding when you need explicit control over which certificate is bound to a specific listener, or when a listener is shared across multiple Ingresses.

Prerequisites

Before you begin, ensure that you have:

• A trusted certificate obtained in one of the following ways:

  • Purchased from Certificate Management Service

  • Purchased from another certificate authority (CA)

  • (Optional) A self-signed certificate generated for testing — see Step 2: Generate a self-signed certificate (optional)

Overview

Step 1: Add an HTTPS listener to the AlbConfig

1. Edit the AlbConfig:

   kubectl edit albconfig <albconfig-name>

2. Add a listener entry for port 443:

   apiVersion: alibabacloud.com/v1
   kind: AlbConfig
   metadata:
     name: alb
   spec:
     config:
       addressAllocatedMode: Fixed
       addressType: Internet
       zoneMappings:
       - vSwitchId: vsw-bp19sXXXXXXX176iv
       - vSwitchId: vsw-bp1boXXXXXXXu74xz
     listeners:
     - port: 80
       protocol: HTTP
     - port: 443       # Adds the HTTPS listener; a certificate is required for this listener
       protocol: HTTPS

Step 2: Generate a self-signed certificate (optional)

Skip this step if you already have a certificate from Certificate Management Service or a CA.

Run the following OpenSSL commands to generate a self-signed certificate:

openssl genrsa -out albtop-key.pem 4096
openssl req -subj "/CN=demo.alb.ingress.top" -sha256 -new -key albtop-key.pem -out albtop.csr
echo subjectAltName = DNS:demo.alb.ingress.top > extfile.cnf
openssl x509 -req -days 3650 -sha256 -in albtop.csr -signkey albtop-key.pem -out albtop-cert.pem -extfile extfile.cnf

Expected output:

Certificate request self-signature ok
subject=CN=demo.alb.ingress.top

Replace demo.alb.ingress.top with your domain name.

Step 3: Create sample resources

In addition to the AlbConfig, you need a Deployment, Service, IngressClass, and Ingress for the ALB Ingress to function.

1. Create a file named https-quickstart.yaml with the following content:

   apiVersion: networking.k8s.io/v1
   kind: IngressClass
   metadata:
     name: https-ingressclass
   spec:
     controller: ingress.k8s.alibabacloud/alb
     parameters:
       apiGroup: alibabacloud.com
       kind: AlbConfig
       name: alb   # Must match the name of your AlbConfig
   ---
   apiVersion: networking.k8s.io/v1
   kind: Ingress
   metadata:
     name: https-ingress
   spec:
     ingressClassName: https-ingressclass
     rules:
     - host: demo.alb.ingress.top   # Replace with your domain name
       http:
         paths:
         - backend:
             service:
               name: https-svc
               port:
                 number: 443
           path: /
           pathType: Prefix
   ---
   apiVersion: apps/v1
   kind: Deployment
   metadata:
     name: https-deploy
   spec:
     replicas: 1
     selector:
       matchLabels:
         app: https-deploy
     template:
       metadata:
         labels:
           app: https-deploy
       spec:
         containers:
           - image: registry.cn-hangzhou.aliyuncs.com/acs-sample/old-nginx:latest
             imagePullPolicy: IfNotPresent
             name: https-deploy
             ports:
               - containerPort: 80
                 protocol: TCP
   ---
   apiVersion: v1
   kind: Service
   metadata:
     name: https-svc
   spec:
     ports:
       - name: port1
         port: 443
         protocol: TCP
         targetPort: 80
     selector:
       app: https-deploy
     sessionAffinity: None
     type: ClusterIP

2. If the AlbConfig has both HTTP and HTTPS listeners, add the listen-ports annotation to the Ingress:

   apiVersion: networking.k8s.io/v1
   kind: Ingress
   metadata:
     name: https-ingress
     annotations:
       alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80},{"HTTPS": 443}]'
   spec:
     # ...

3. Apply the resources:

   kubectl apply -f https-quickstart.yaml

Step 4: Configure certificates

Choose one of the following methods.

Step 5: Verify the result

1. Get the Ingress address:

   kubectl get ingress

   Expected output:

   NAME            CLASS                HOSTS                  ADDRESS                         PORTS     AGE
   https-ingress   https-ingressclass   demo.alb.ingress.top   alb-********.alb.aliyuncs.com   80, 443   83m

   Note the values in the HOSTS and ADDRESS columns.

2. Send an HTTPS request to the backend Service:

   curl -H HOST:demo.alb.ingress.top -k https://alb-********.alb.aliyuncs.com

   Replace demo.alb.ingress.top and alb-********.alb.aliyuncs.com with the values from the previous step. If the certificate is configured correctly, the command returns:

   old

What's next

• To receive requests from clients that use the HTTP/3 protocol, see Use QUIC listeners to support HTTP/3 and improve network performance.

• To enable HTTPS mutual authentication on a listener, see Use HTTPS mutual authentication to enhance service security.