tencent cloud

1. Log in to the TKE console and select Cluster on the left sidebar.
2. On the Cluster Management page, select the ID of the cluster for which to modify the Ingress.
3. On the cluster details page, select Services and Routes > Ingress as shown below:
   
4. Click Create and configure the relevant redirection rule on the Create Ingress page as shown below:
   • None: no redirection rules are used.
   • Manual: the Redirection Forwarding Configuration section will appear under Forwarding Configuration.
     • You can enter information in Forwarding Configuration just like for a general Ingress, with the backend being a certain service.
     • You can also enter information in Redirection Forwarding Configuration just like for a general Ingress, but the backend is a certain path in a certain "forwarding configuration".
       
   • Auto: it only takes effect for the "HTTPS" path in Forwarding Configuration. The same path with the "HTTP" protocol will be generated automatically, and only the protocols are different. The forwarding rule for the "HTTP" path is automatically redirected to the "HTTPS" path.
     

Automatic redirection: HTTP redirection to HTTPS

Note

It takes effect only for the forwarding rule of the HTTPS protocol.

ingress.cloud.tencent.com/auto-rewrite: "true"

Manual redirection

Manual redirection requires adding an annotation and modifying an annotation:

• Added annotation:
  
  ingress.cloud.tencent.com/rewrite-support: "true"  # Indicate that redirection is allowed

• Modified annotation:
  
  # Format of the original annotation:
  {
      "host": "<domain>",
      "path": "<path>",
      "backend": {
          "serviceName": "<service name="">",
          "servicePort": "<service port="">"
      }
  }
  
  # Format of the new annotation:
  {
      "host": "<domain>",
      "path": "<path>",
      "backend": {
          "serviceName": "<service name="">",
          "servicePort": "<service port="">"
      },
      "rewrite": {
          "port": "<rewrite-port>",
          "host": "<rewrite-domain>",
          "path": "<rewrite-path>"
      }
  }

Samples

A service was previously accessed at 121.4.25.44/path2, and after a new version is released, it is expected to be accessed at 121.4.25.44/v2/path2. To do this, you can make the following modification:

• Add an annotation:
  
  ingress.cloud.tencent.com/rewrite-support: "true"   # Allow redirection

• Modify the original annotation:
  
  # Replace /v1/path1 with /path1 port 80 and /v2/path2 with /path2 port 80. Note: the host can be omitted
  kubernetes.io/ingress.http-rules: '
  [{
          "path": "/path1",
          "backend": {
              "serviceName": "path1",
              "servicePort": "80"
          }
      },
      {
          "path": "/path2",
          "backend": {
              "serviceName": "path2",
              "servicePort": "80"
          }
      },
      {
          "path": "/v1/path1",
          "rewrite": {
              "port": 80,
              "path": "/path1"
          }
      },
      {
          "path": "/v2/path2",
          "rewrite": {
              "port": 80,
              "path": "/path2"
          }
      }
  ]'

  Modified YAML:
  
  apiVersion: extensions/v1beta1
  kind: Ingress
  metadata: 
    annotations: 
      description: test
      ingress.cloud.tencent.com/rewrite-support: "true"
      kubernetes.io/ingress.class: qcloud
      kubernetes.io/ingress.http-rules: '[{"path":"/path1","backend":{"serviceName":"path1","servicePort":"80"}},{"path":"/path2","backend":{"serviceName":"path2","servicePort":"80"}},{"path":"/v1/path1","rewrite":{"port":80,"path":"/path1"}},{"path":"/v2/path2","rewrite":{"port":80,"path":"/path2"}}]'
      kubernetes.io/ingress.https-rules: "null"
      kubernetes.io/ingress.rule-mix: "true"
    name: test
    namespace: default
  spec: 
    rules: 
    - http: 
        paths: 
        - backend: 
            serviceName: path1
            servicePort: 80
          path: /path1
          pathType: ImplementationSpecific
    - http: 
        paths: 
        - backend: 
            serviceName: path2
            servicePort: 80
          path: /path2
          pathType: ImplementationSpecific
  status: 
    loadBalancer: 
      ingress: 
      - ip: 121.4.25.44

  For detailed Ingress annotations, please see Ingress Annotation.