Help Center/ Cloud Container Engine/ User Guide (Paris Regions)/ Network/ Ingresses/ ELB Ingresses/ Interconnecting ELB Ingresses with HTTPS Backend Services
Updated on 2024-01-26 GMT+08:00
View PDF
Share

Interconnecting ELB Ingresses with HTTPS Backend Services

Ingress can interconnect with backend services of different protocols. By default, the backend proxy channel of an ingress is an HTTP channel. To create an HTTPS channel, add the following configuration to the annotations field:

kubernetes.io/elb.pool-protocol: https

Constraints

  • This feature only applies to clusters of v1.23.8, v1.25.3, and later.
  • Ingress can interconnect with HTTPS backend services only when dedicated load balancers are used.
  • When interconnecting with HTTPS backend services, set Client Protocol of ingress to HTTPS.

Interconnecting with HTTPS Backend Services

An ingress configuration example:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: ingress-test
  namespace: default
  annotations:
    kubernetes.io/elb.port: '443'
    kubernetes.io/elb.id: <your_elb_id>    # In this example, an existing dedicated load balancer is used. Replace its ID with the ID of your dedicated load balancer.
    kubernetes.io/elb.class: performance
    kubernetes.io/elb.pool-protocol: https  # Interconnected HTTPS backend service
    kubernetes.io/elb.tls-ciphers-policy: tls-1-2
spec:
  tls: 
    - secretName: ingress-test-secret
  rules:
    - host: ''
      http:
        paths:
          - path: '/'
            backend:
              service:
                name: <your_service_name>  # Replace it with the name of your target Service.
                port:
                  number: 80
            property:
              ingress.beta.kubernetes.io/url-match-mode: STARTS_WITH
            pathType: ImplementationSpecific
  ingressClassName: cce
Parent topic: ELB Ingresses