Redirecting HTTP to HTTPS for a LoadBalancer Ingress
Ingresses can forward HTTP access requests to HTTPS listeners. The following is an example for redirecting the requests for accessing example.com/test of an ingress to HTTPS port 443.
Prerequisites
- An ingress provides network access for backend workloads. Ensure that a workload is available in a cluster. If no workload is available, deploy a workload by referring to Creating a Deployment, Creating a StatefulSet, or Creating a DaemonSet.
- You have created a Service for the workload. Services Supported by LoadBalancer Ingresses lists the Service types supported by LoadBalancer ingresses.
Notes and Constraints
- The advanced forwarding policy of LoadBalancer ingresses is available only to dedicated load balancers.
- The advanced forwarding policy of LoadBalancer ingresses is available only in clusters of version v1.23.14-r0, v1.25.9-r0, v1.27.6-r0, v1.28.4-r0, or later.
Redirecting HTTP to HTTPS
You can configure HTTP to HTTPS redirection using either the CCE console or kubectl.
- Log in to the CCE console and click the cluster name to access the cluster console.
- Choose Services & Ingresses in the navigation pane, click the Ingresses tab, and click Create Ingress in the upper right corner.
- Configure ingress parameters.
This example explains only key parameters for redirecting HTTP to HTTPS. You can configure other parameters as required. For details, see Creating a LoadBalancer Ingress on the Console.
Table 1 Key parameters Parameter
Description
Example
Name
Enter an ingress name.
ingress-test
Load Balancer
Select a load balancer to be associated with the ingress or automatically create a load balancer. In this example, only dedicated load balancers are supported.
Dedicated
Listener
- External Protocol: HTTP and HTTPS are available.
- External Port: specifies the port of the load balancer listener.
- Redirect to HTTPS: After this function is enabled, you can configure the HTTPS port.
- External Port: Enter an HTTPS port.
- Certificate Source: TLS secret and ELB server certificates are supported.
- Server Certificate: Use a certificate created on ELB.
If no certificate is available, go to the ELB console and create one. For details, see Adding a Certificate.
- External Protocol: HTTP
- External Port: 80
- Redirect to HTTPS: enabled
- External Port: 443
- Certificate Source: ELB server certificate
- Server Certificate: cert-test
Forwarding Policy
- Domain Name: Enter an actual domain name to be accessed. If it is left blank, the ingress can be accessed through the IP address. Ensure that the domain name has been registered and licensed. Once a forwarding policy is configured with a domain name specified, you must use the domain name for access.
- Path Matching Rule: Select Prefix match, Exact match, or RegEx match.
- Path: Enter the path provided by a backend application for external access. The path added must be valid in the backend application, or the forwarding cannot take effect.
- Destination Service: Select an existing Service or create a Service. Any Services that do not match the search criteria will be filtered out automatically.
- Destination Service Port: Select the access port of the destination Service.
- Domain Name: You do not need to configure this parameter.
- Path Matching Rule: RegEx match
- Path: /
- Destination Service: nginx
- Destination Service Port: 80
Figure 1 Redirecting HTTP to HTTPS
Figure 2 Configuring a port for redirecting HTTP to HTTPS
- Click OK.
You can use annotations to redirect the requests of an ingress to an HTTPS listener. The following is an example:
- Use kubectl to access the cluster. For details, see Connecting to a Cluster Using kubectl.
- Create a YAML file named ingress-test.yaml. The file name can be customized.
vi ingress-test.yaml
An example YAML file of an ingress associated with an existing load balancer is as follows:
apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: test-redirect-listener namespace: default annotations: kubernetes.io/elb.id: df76342f-e898-402a-bac8-bde5bf974da8 kubernetes.io/elb.class: performance kubernetes.io/elb.listen-ports: '[{"HTTP":80},{"HTTPS":443}]' # Multi-port configuration kubernetes.io/elb.ssl-redirect: 'true' # Enable redirection from HTTP to HTTPS. kubernetes.io/elb.tls-certificate-ids: 6cfb43c9de1a41a18478b868e34b0a82 # HTTPS listener server certificate spec: rules: - host: '' http: paths: - path: / backend: service: name: test-service port: number: 80 property: ingress.beta.kubernetes.io/url-match-mode: STARTS_WITH pathType: ImplementationSpecific ingressClassName: cce
Table 2 Key parameters Parameter
Mandatory
Type
Description
kubernetes.io/elb.listen-ports
Yes
String
Multi-port listening configuration, which cannot be modified after being configured.
Format: The value is a JSON string, for example:
[{"HTTP":80},{"HTTPS":443}]
Parameter: The port number ranges from 1 to 65535.
kubernetes.io/elb.ssl-redirect
Yes
String
Whether to enable redirection from HTTP to HTTPS.
Format: The value can be true or false.
Parameter: true indicates that redirection is enabled. If the value is false or the parameter is unavailable, redirection is disabled.
Either this annotation or the annotation of a grayscale release can be configured.
- Create an ingress.
kubectl create -f ingress-test.yaml
If information similar to the following is displayed, the ingress has been created:
ingress/test-redirect-listener created
- Check the created ingress.
kubectl get ingress
If information similar to the following is displayed, the ingress has been created:
NAME CLASS HOSTS ADDRESS PORTS AGE test-redirect-listener cce * 121.**.**.** 80 10s
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot