Container Compute Service:Sesuaikan aturan routing Ingress ALB

Arahkan traffic berdasarkan IP sumber dan header permintaan

Ingress berikut mengarahkan permintaan ke gray-hello hanya jika ketiga kondisi terpenuhi: IP sumber berada dalam 192.168.0.0/16 atau 172.16.0.0/16, nilai header gray-hello adalah value1 atau value2, dan path-nya adalah /hello. Permintaan lainnya dialihkan ke Service lain.

alb.ingress.kubernetes.io/order menetapkan prioritas Ingress — nilai lebih rendah memiliki prioritas lebih tinggi.

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    alb.ingress.kubernetes.io/order: "1"
    alb.ingress.kubernetes.io/conditions.gray-hello: |
      [{
        "type": "Header",
        "headerConfig": {
          "key": "gray-hello",
          "values": [
            "value1",
            "value2"
          ]
        }
       },
       {
         "type": "SourceIp",
         "sourceIpConfig": {
           "values": [
             "192.168.0.0/16",
             "172.16.0.0/16"
           ]
         }
      }]
  name: gray-hello
spec:
  ingressClassName: alb
  rules:
    - http:
        paths:
          - path: /hello
            pathType: ImplementationSpecific
            backend:
              service:
                name: gray-hello
                port:
                  number: 88

Arahkan traffic berdasarkan nama domain, metode permintaan, dan cookie

Ingress berikut mengarahkan permintaan ke service-a hanya jika semua kondisi cocok: domain adalah www.hostvalue1.edu atau www.hostvalue2.edu, metodenya adalah GET atau HEAD, cookie cookiekey1 bernilai cookievalue1, dan path-nya adalah /test. Permintaan lainnya dialihkan ke service-b.

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    alb.ingress.kubernetes.io/conditions.service-a: |
      [{
        "type": "Cookie",
        "cookieConfig": {
          "values": [
            {
              "key": "cookiekey1",
              "value": "cookievalue1"
            }
          ]
        }
       },
       {
        "type": "Method",
        "methodConfig": {
          "values": [
            "GET",
            "HEAD"
          ]
        }
       },
       {
        "type": "Host",
        "hostConfig": {
          "values": [
            "www.hostvalue1.edu",
            "www.hostvalue2.edu"
          ]
        }
      }]
  name: ingress-example
spec:
  ingressClassName: alb
  rules:
    - http:
        paths:
          - path: /test
            pathType: ImplementationSpecific
            backend:
              service:
                name: service-a
                port:
                  number: 88
          - path: /test
            pathType: ImplementationSpecific
            backend:
              service:
                name: service-b
                port:
                  number: 88

Arahkan traffic berdasarkan string kueri, beberapa header permintaan, dan beberapa path

Ingress berikut mengarahkan permintaan ke service-a jika semua kondisi cocok: path adalah /pathvalue1, /pathvalue2, atau /test; string kueri querystringkey1 bernilai querystringvalue2; header headerkey1 bernilai headervalue1 atau headervalue2; dan header headerkey2 bernilai headervalue3 atau headervalue4. Permintaan lainnya dialihkan ke service-b.

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    alb.ingress.kubernetes.io/conditions.service-a: |
      [{
        "type": "Path",
        "pathConfig": {
          "values": [
            "/pathvalue1",
            "/pathvalue2"
          ]
        }
       },
       {
        "type": "QueryString",
        "queryStringConfig": {
          "values": [
            {
              "key": "querystringkey1",
              "value": "querystringvalue2"
            }
          ]
        }
       },
       {
        "type": "Header",
        "headerConfig": {
          "key": "headerkey1",
          "values": [
            "headervalue1",
            "headervalue2"
          ]
        }
       },
       {
        "type": "Header",
        "headerConfig": {
          "key": "headerkey2",
          "values": [
            "headervalue3",
            "headervalue4"
          ]
        }
      }]
  name: ingress-example
spec:
  ingressClassName: alb
  rules:
    - http:
        paths:
          - path: /test
            pathType: ImplementationSpecific
            backend:
              service:
                name: service-a
                port:
                  number: 88
          - path: /test
            pathType: ImplementationSpecific
            backend:
              service:
                name: service-b
                port:
                  number: 88

Kembalikan respons tetap dengan kode status 503

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  namespace: default
  name: ingress
  annotations:
    alb.ingress.kubernetes.io/actions.insert-header: |
      [{
        "type": "InsertHeader",
        "InsertHeaderConfig": {
          "key": "source",
          "value": "alibaba",
          "valueType": "UserDefined"
        }
      }]
spec:
  ingressClassName: alb
  rules:
    - http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: insert-header
                port:
                  number: 80

Arahkan permintaan ke HTTPS menggunakan 301

Ingress berikut mengalihkan semua permintaan HTTP ke HTTPS menggunakan pengalihan permanen 301.

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  namespace: default
  name: ingress
  annotations:
    alb.ingress.kubernetes.io/actions.redirect: |
      [{
        "type": "Redirect",
        "RedirectConfig": {
          "host": "${host}",
          "path": "${path}",
          "port": "${port}",
          "protocol": "https",
          "query": "${query}",
          "httpCode": "301"
        }
      }]
spec:
  ingressClassName: alb
  rules:
    - http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: redirect
                port:
                  name: use-annotation # Harus use-annotation untuk aksi pengalihan

Parameter RedirectConfig:

Sisipkan header permintaan

Ingress berikut menyisipkan header source: alibaba ke semua permintaan sebelum meneruskannya ke backend. Jika header tersebut sudah ada, nilainya akan ditimpa.

Nama Service dalam anotasi harus sesuai dengan nama Service pada bidang backend.

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  namespace: default
  name: ingress
  annotations:
    alb.ingress.kubernetes.io/actions.insert-header: |
      [{
        "type": "InsertHeader",
        "InsertHeaderConfig": {
          "key": "source",
          "value": "alibaba",
          "valueType": "UserDefined"
        }
      }]
spec:
  ingressClassName: alb
  rules:
    - http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: insert-header
                port:
                  number: 80

Cerminkan traffic ke grup server

Ingress berikut mencerminkan semua traffic yang cocok dengan demo.domain.ingress.top/test ke grup server tertentu sambil tetap meneruskan permintaan aslinya secara normal.

Untuk mendapatkan ID grup server, login ke konsol Server Load Balancer (SLB), pilih ALB > Server Groups, lalu temukan ID-nya di halaman Server Groups.

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: traffic-mirror-ingress
  annotations:
    # Nama Service dalam anotasi harus sesuai dengan nama Service pada bidang backend.
    alb.ingress.kubernetes.io/actions.traffic-mirror: |
      [{
        "type": "TrafficMirror",
        "TrafficMirrorConfig": {
          "TargetType": "ForwardGroupMirror",
          "MirrorGroupConfig": {
            "ServerGroupTuples": [{
              "ServerGroupID": "sgp-2auud2fxj1r46*****"
            }]
          }
        }
      }]
spec:
  ingressClassName: alb
  rules:
    - host: demo.domain.ingress.top
      http:
        paths:
          - path: /test
            pathType: Prefix
            backend:
              service:
                name: traffic-mirror
                port:
                  number: 80

Teruskan permintaan ke beberapa grup server backend

Distribusikan permintaan ke beberapa grup server backend berdasarkan bobot.

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: forward-ingress
  annotations:
    # Nama Service dalam anotasi harus sesuai dengan nama Service pada bidang backend.
    alb.ingress.kubernetes.io/actions.forward: |
      [{
        "type": "ForwardGroup",
        "ForwardConfig": {
          "ServerGroups": [{
            "ServiceName": "tea-svc",
            "Weight": 80,
            "ServicePort": 80
          },
          {
            "ServiceName": "coffee-svc",
            "Weight": 20,
            "ServicePort": 80
          }]
        }
      }]
spec:
  ingressClassName: alb
  rules:
    - host: demo.domain.ingress.top
      http:
        paths:
          - path: /path
            pathType: Prefix
            backend:
              service:
                name: forward
                port:
                  name: use-annotation # Harus use-annotation untuk aksi forward

alb.ingress.kubernetes.io/actions.forward: |
  [{
    "type": "ForwardGroup",
    "ForwardConfig": {
      "ServerGroups": [{
        "ServerGroupID": "sgp-71aexb9y93ypo*****",
        "Weight": 80
      },
      {
        "ServerGroupID": "sgp-slygpbvm2cydo*****",
        "Weight": 20
      }]
    }
  }]

Tulis ulang nama domain, path, atau string kueri

Ingress berikut menulis ulang nama domain menjadi demo.domain.ingress.top, path menjadi /test, dan string kueri menjadi querystring untuk semua permintaan yang cocok dengan /path.

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  namespace: default
  name: rewrite-ingress
  annotations:
    alb.ingress.kubernetes.io/actions.rewrite: |
      [{
        "type": "Rewrite",
        "RewriteConfig": {
          "Host": "demo.domain.ingress.top",
          "Path": "/test",
          "Query": "querystring"
        }
      }]
spec:
  ingressClassName: alb
  rules:
    - http:
        paths:
          - path: /path
            pathType: Prefix
            backend:
              service:
                name: rewrite
                port:
                  number: 80

Untuk informasi selengkapnya tentang aturan rewrite, lihat Konfigurasi aturan penulisan ulang.

Modifikasi header respons berdasarkan nilai header respons

Secara default, aturan routing kustom berlaku untuk lalu lintas masuk. Untuk menerapkan aturan pada lalu lintas keluar (respons), atur alb.ingress.kubernetes.io/rule-direction.<service-name> menjadi Response.

Ingress berikut menyisipkan header source: alibaba ke respons ketika respons tersebut sudah berisi header response-hello dengan nilai value1 atau value2.

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    alb.ingress.kubernetes.io/rule-direction.response-header: Response
    alb.ingress.kubernetes.io/conditions.response-header: |
      [{
        "type": "ResponseHeader",
        "responseHeaderConfig": {
          "key": "response-hello",
          "values": [
            "value1",
            "value2"
          ]
        }
      }]
    alb.ingress.kubernetes.io/actions.response-header: |
      [{
        "type": "InsertHeader",
        "InsertHeaderConfig": {
          "key": "source",
          "value": "alibaba",
          "valueType": "UserDefined"
        }
      }]
  name: response-header
spec:
  ingressClassName: alb
  rules:
    - http:
        paths:
          - path: /
            pathType: ImplementationSpecific
            backend:
              service:
                name: response-header
                port:
                  name: use-annotation # Harus use-annotation untuk aturan routing arah keluar

Hapus header respons berdasarkan kode status respons

Ingress berikut menghapus header response-hello dari respons yang mengembalikan kode status 200 atau 300.

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    alb.ingress.kubernetes.io/rule-direction.response-hello: Response
    alb.ingress.kubernetes.io/conditions.response-hello: |
      [{
        "type": "ResponseStatusCode",
        "responseStatusCodeConfig": {
          "values": [
            "200",
            "300"
          ]
        }
      }]
    alb.ingress.kubernetes.io/actions.response-hello: |
      [{
        "type": "RemoveHeader",
        "RemoveHeaderConfig": {
          "key": "response-hello"
        }
      }]
  name: response-hello
spec:
  ingressClassName: alb
  rules:
    - http:
        paths:
          - path: /*
            pathType: ImplementationSpecific
            backend:
              service:
                name: response-hello
                port:
                  name: use-annotation # Harus use-annotation untuk aturan routing arah keluar

Batasi laju permintaan dengan Pembatasan laju QPS

Tetapkan batas laju permintaan global, batas laju per IP client, atau keduanya. Aksi Pembatasan laju QPS harus digabungkan dengan aksi forward.

annotations:
  alb.ingress.kubernetes.io/actions.traffic-limit: |
    [{
      "type": "TrafficLimit",
      "TrafficLimitConfig": {
        "QPS": "1000",
        "QPSPerIp": "100"
      }
    }]