{
    "name": "...",
    "domains": [],
    "routes": [],
    "require_tls": "...",
    "virtual_clusters": [],
    "rate_limits": [], 
    "request_headers_to_add": [], 
    "request_headers_to_remove": [], 
    "response_headers_to_add": [], 
    "response_headers_to_remove": [], 
    "cors": "{...}",
    "per_filter_config": "{...}", 
    "typed_per_filter_config": "{...}", 
    "include_request_attempt_count": "...", 
    "retry_policy": "{...}",
    "hedge_policy": "{...}"
}

listeners:
- name:
	address: {...} 
	filter_chians: [] 
	- filters:
		- name: envoy.http_connection_manager
			config:
				...
				route_config:
					name: ... 
					virutal_hosts: [] 
					- name: ...
						domains: []    # 虚拟主机的域名，路由匹配时将请求报文中的host标头值与此处列表项进行匹配检测;
						routes: []			# 路由条目，匹配到当前虚拟主机的请求中的path匹配检测将针对各route中由match定义条件进行;
						- name: ...
							match: {...}
								prefix|path|regex: ... # 基于路径前缀、路径或正则表达式三者之一定义匹配条件;
							route: {...}
								cluster|cluster_header|weighted_cluster: ... # 基于集群、请求报文中的集群标头或加权集群(流量分割)定义路由目标;
						virtual_clusters: [] # 为此虚拟主机定义的用于收集统计信息的虚拟集群列表;
						...
					...

{
    "name": "...",
    "match": "{...}",
    "route": "{...}",
    "redirect": "{...}",
    "direct_response": "{...}",
    "metadata": "{...}",
    "decorator": "{...}",
    "per_filter_config": "{...}",
    "typed_per_filter_config": "{...}",
    "request_headers_to_add": [],
    "request_headers_to_remove": [],
    "response_headers_to_add": [],
    "response_headers_to_remove": [],
    "tracing": "{...}"
}

{
  "prefix": "...",
  "path": "...",
  "regex": "...", 
  "case_sensitive": "{...}",
  "runtime_fraction": "{...}", 
  "headers": [], 
  "query_parameters": [], 
  "grpc": "{...}"
}

          route_config:
            name: local_route
            virtual_hosts:
            - name: vh_001
              domains: ["ilinux.io", "*.ilinux.io", "ilinux.*"]
              routes:
              - match:
                  path: "/service/blue"
                route:
                  cluster: blue
              - match:
                  regex: "^/service/.*blue$"
                redirect:
                  path_redirect: "/service/blue"
              - match:
                  prefix: "/service/yellow"
                direct_response:
                  status: 200
                  body:
                    inline_string: "This page will be provided soon later.\n"
              - match:
                  prefix: "/"
                route:
                  cluster: red
            - name: vh_002
              domains: ["*"]
              routes:
              - match:
                  prefix: "/"
                route:
                  cluster: gray

          route_config:
            name: local_route
            virtual_hosts:
            - name: vh_001
              domains: ["*"]
              routes:
              - match:
                  prefix: "/"
                  headers:   # 基于header匹配
                  - name: X-Canary
                    exact_match: "true"
                route:
                  cluster: ver-1.7-pre
              - match:
                  prefix: "/"
                  query_parameters:  #基于参数匹配
                  - name: "username"
                    string_match:
                      prefix: "vip_"
                route:
                  cluster: ver-1.6
              - match:
                  prefix: "/"
                route:
                  cluster: ver-1.5

{
  "cluster": "...",   # 路由到指定的目标集群
  "cluster_header": "...",
  "weighted_clusters": "{...}",  #将流量路由并按权重比例分配到多个上游集群；
  "cluster_not_found_response_code": "...",
  "metadata_match": "{...}",
  "prefix_rewrite": "...",
  "host_rewrite": "...",
  "auto_host_rewrite": "{...}",
  "auto_host_rewrite_header": "...",
  "timeout": "{...}",
  "idle_timeout": "{...}",
  "retry_policy": "{...}",
  "request_mirror_policy": "{...}",
  "priority": "...",
  "rate_limits": [],
  "include_vh_rate_limits": "{...}",
  "hash_policy": [],
  "cors": "{...}",
  "max_grpc_timeout": "{...}",
  "grpc_timeout_offset": "{...}",
  "upgrade_configs": [],
  "internal_redirect_action": "...",
  "hedge_policy": "{...}"
}

{
    "https_redirect": "...",
    "scheme_redirect": "...",
    "host_redirect": "...",
    "port_redirect": "...",
    "path_redirect": "...",
    "prefix_rewrite": "...",
    "response_code": "...",
    "strip_query": "..."
}

{
  "status": "...",
  "body": "{...}" 
}

{
	"filename": "...", 
  "inline_bytes": "...", 
  "inline_string": "..."
}

root@istio:~/ServiceMesh_in_Practise/http-connection-manager/httproute-simple-match# ls
docker-compose.yaml  front-envoy.yaml

root@istio:~/ServiceMesh_in_Practise/http-connection-manager/httproute-header-match# ls
docker-compose.yaml  front-envoy.yaml

routes:
- match:			# 定义路由匹配参数;
		prefix|path|regex: ... 		# 流量过滤条件，三者必须定义其中之一;也可结合基于header和parameter的过滤条件
		runtime_fraction:					# 额外匹配指定的运行时键值，每次评估匹配路径时，它必需低于此字段指示的匹配百分比;支持渐进式修改;
			default_value:          # 运行时键值不可用时，则使用此默认值;
				numerator:						# 指定分子，默认为0;
				denominator:					# 指定分母，小于分子时，最终百分比为1;分母可固定使用HUNDRED(默认)、TEN_THOUSAND和MILLION;
			runtime_key: routing.traffic_shift.app1   # 指定要使用的运行时键，键值需要用户自定义，用于运行时修改分子的值;
	route:
		custer: app1_v1
- match:
		prefix|path|regex: ...      # 此处的匹配条件应该与前一个路由匹配条件相同，以确保能够分割流量;
	route:
		cluster: app1_v2            # 此处的集群通常是前一个路由项目中的目标集群应用程序的不同版本;	

# curl -X POST 'http://envoy_ip:admin_port/runtime_modify?key1=val1&key2=val2'
例如：
# curl -X POST 'http://172.16.0.2:9901/runtime_modify?routing.traffic_shift.app1=30'

root@istio:~/ServiceMesh_in_Practise/http-connection-manager/http-traffic-shifting# ls
docker-compose.yaml  front-envoy.yaml  send-request.sh

routes
- match: {...}
	route:
		weight_clusters: {...}
			clusters: []  # 与当前路由关联的一个或多个集群，必须参数
			- name: ...
				weight: ...   #集群权重，取值范围：0至total_weight
				metadata_match: {...}  # 子集负载均衡器使用的端点元数据匹配条件，可选参数，仅用于上游集群中具有与此字段中设置的元数据匹配的元数端点以进行流量分配;
			total_weight: ...  # 总权重值，默认为100;
			runtime_key_prefix: ... # 可选参数，用于设定键前缀，从而每个集群以“runtime_key_prefix+.+cluster[i].name”为其键名，并能够以运行时键值的方式为每个集群提供权重;其中cluster[i].name表示列表中第i个集群名称。
			...

root@istio:~/ServiceMesh_in_Practise/http-connection-manager/http-traffic-splitting# ls
docker-compose.yaml  front-envoy.yaml  send-request.sh

route:
  cluster: myapp-v1.5
  request_mirror_policy:
    cluster: myapp-v1.6  # 影子集群名称
    #runtime_key: "..."  # 备注：即将废弃
    runtime_fraction:
      default_value:
        numerator: 10
        denominator: HUNDRED
      runtime_key: routing.request_mirror.myapp

root@istio:~/ServiceMesh_in_Practise/http-connection-manager/http-request-mirror# ls
docker-compose.yaml  front-envoy.yaml  send-request.sh

{
"delay": "{...}", # 注入延迟，延迟和请求中止至少要定义一个; 
"abort": "{...}", # 注入请求中止
"upstream_cluster": "...",  # 过路器适配的上游集群，即仅生效于指定的目标集群;
"headers": [], # 过滤器适配的请求报文标头列表，匹配检测时，各标头间为“与”关系; 
"downstream_nodes": [], # 要注入故障的下游主机列表，未指定时将匹配所有主机;
"max_active_faults": "{...}",  # 在同一个时间点所允许的最大活动故障数，默认为不限制;可以被
                                # 运行时参数config_http_filters_fault_injection_runtime所覆盖;
"response_rate_limit": "{...}" # 响应速率限制，可以被运行时参数fault.http.rate_limit.response_percent所覆盖;此为单流或连接级别的限制
}

http_filters:
- name: envoy.fault
  config:
    delay:
      type: fixed
      fixed_delay: 10s
      percentage:
        numerator: 10
        denominator: HUNDRED

http_filters:
- name: envoy.fault
  config:
    abort:
      http_status: 503
      percentage:
        numerator: 10
        denominator: HUNDRED

root@istio:~/ServiceMesh_in_Practise/http-connection-manager/fault-injection# ls
docker-compose.yaml  front-envoy.yaml  service-envoy-fault-injection-abort.yaml  service-envoy-fault-injection-delay.yaml  service-envoy.yaml

routes:
- match:
    prefix: "/service/blue"
  route:
    cluster: blue_abort
    retry_policy:
      retry_on: "5xx"  # 重试
      num_retries: 3
- match:
    prefix: "/service/red"
  route:
    cluster: red_delay
    timeout: 1s         # 超时
- match:
    prefix: "/service/green"
  route:
    cluster: green
- match:
    prefix: "/"
  route:
    cluster: mycluster

root@istio:~/ServiceMesh_in_Practise/http-connection-manager/timeout-retries# ls
docker-compose.yaml  front-envoy.yaml  service-envoy-fault-injection-abort.yaml  service-envoy-fault-injection-delay.yaml  service-envoy.yaml

              routes:
              - match:
                  prefix: "/cors/open"
                route:
                  cluster: backend_service
              - match:
                  prefix: "/cors/disabled"
                route:
                  cluster: backend_service
                  cors:
                    filter_enabled:
                      default_value:
                        numerator: 0
                        denominator: HUNDRED
              - match:
                  prefix: "/cors/restricted"
                route:
                  cluster: backend_service
                  cors:
                    allow_origin:
                    - "envoyproxy.io"
                    allow_methods: "GET"
              - match:
                  prefix: "/"
                route:
                  cluster: backend_service
          http_filters:
          - name: envoy.cors
            typed_config: {}
          - name: envoy.router
            typed_config: {}

root@istio:~/ServiceMesh_in_Practise/http-connection-manager/cors# ls
README.md  backend  frontend