clusters:
- name: ...
	... 
	load_assignment: 
	endpoints:
	- lb_endpoints:
		- endpoint: 
				health_check_config:
					port_value: ... # 自定义健康状态检测时使用的端口; 如果未定义，则向endpoint的端口发送检测
				...
			...
	health_checks:
	- timeout: ... # 超时时长
		interval: ... # 时间间隔
		initial_jitter: ... # 初始检测时间点散开量，以毫秒为单位;
		interval_jitter: ... # 间隔检测时间点散开量，以毫秒为单位;
		unhealthy_threshold: ... # 将主机标记为不健康状态的检测阈值，即至少多少次不健康的检测后才将其标记为不可用; 	
		healthy_threshold: ... # 将主机标记为健康状态的检测阈值，但初始检测成功1次即视主机为健康;
		http_health_check: {...} # HTTP类型的检测;包括此种类型在内的以下四种检测类型必须设置一种;
		tcp_health_check: {...} # TCP类型的检测;
		grpc_health_check: {...} # GRPC专用的检测;
		custom_health_check: {...} # 自定义检测;
		reuse_connection: ... # 布尔型值，是否在多次检测之间重用连接，默认值为true;
		no_traffic_interval: ... # 定义未曾调度任何流量至集群时其端点健康检测时间间隔，一旦其接收流量即转为正常的时间间隔; 
		unhealthy_interval: ... # 标记为“unhealthy”状态的端点的健康检测时间间隔，一旦重新标记为“healthy”即转为正常时间间隔; 
		unhealthy_edge_interval: ... # 端点刚被标记为“unhealthy”状态时的健康检测时间间隔，随后即转为同unhealthy_interval的定义; 
		healthy_edge_interval: ... # 端点刚被标记为“healthy”状态时的健康检测时间间隔，随后即转为同interval的定义;

clusters:
- name: local_service
	connect_timeout: 0.25s 
	lb_policy: ROUND_ROBIN 
	type: EDS 
	eds_cluster_config:
		eds_config:
    	api_config_source:
				api_type: GRPC 
				grpc_services:
				- envoy_grpc:
						cluster_name: xds_cluster 
	health_checks:  #定义tcp检测
	- timeout: 5s
		interval: 10s 
		unhealthy_threshold: 2 
		healthy_threshold: 2 
		tcp_health_check: {}  #对于tcp检测，为空载或非空载

{
	"send": "{...}",
	"receive": [] 
}
 

health_checks: [] 
- ...
	http_health_check:
		"host": "..." # 检测时使用的主机标头，默认为空，此时使用集群名称; 
		"path": "..." # 检测时使用的路径，例如/healthz;必选参数; 
		"service_name": "..." # 用于验证检测目标集群的服务名称参数，可选; 
		"request_headers_to_add": [] # 向检测报文添加的自定义标头列表; 
		"request_headers_to_remove": [] # 从检测报文中移除的标头列表; 
		"use_http2": "..." # 是否使用http2协议;
		"expected_statuses": [] # 期望的响应码列表;
 

clusters:
- name: local_service
	connect_timeout: 0.25s 
	lb_policy: ROUND_ROBIN 
	type: EDS 
	eds_cluster_config:
		eds_config: 
			api_config_source:
				api_type: GRPC 
				grpc_services:
				- envoy_grpc:
						cluster_name: xds_cluster
	health_checks:
	- timeout: 5s
		interval: 10s 
		unhealthy_threshold: 2 
		healthy_threshold: 2 
		http_health_check:
			host: ... # 默认为空值，并自动使用集群为其值; 
			path: ... # 检测针对的路径，例如/healthz; 
			expected_statuses: ... # 期望的响应码，默认为200;

root@istio:~/ServiceMesh_in_Practise/cluster-manager/health-check# ls
README.md  docker-compose.yaml  front-envoy-tcp.yaml  front-envoy.yaml

clusters:
- name: ...
	... 
	outlier_detection:
		consecutive_5xx: ... # 因连续5xx错误而弹出主机之前允许出现的连续5xx响应或本地原始错误的数量，默认为5;
		interval: ... # 弹射分析扫描之间的时间间隔，默认为10000ms或10s;
		base_ejection_time: ... # 主机被弹出的基准时长，实际时长等于基准时长乘以主机已经弹出的次数;默认为30000ms或30s; 
		max_ejection_percent: ... # 因异常探测而允许弹出的上游集群中的主机数量百分比，默认为10%;不过，无论如何，至少要弹出一个主机; 
		enforcing_consecutive_5xx: ... # 基于连续的5xx检测到主机异常时主机将被弹出的几率，可用于禁止弹出或缓慢弹出;默认为100; 
		enforcing_success_rate: ... # 基于成功率检测到主机异常时主机将被弹出的几率，可用于禁止弹出或缓慢弹出;默认为100; 
		success_rate_minimum_hosts: ... # 对集群启动成功率异常检测的最少主机数，默认值为5;
		success_rate_request_volume: ... # 在检测的一次时间间隔中必须收集的总请求的最小值，默认值为100;
		success_rate_stdev_factor: ... # 用确定成功率异常值弹出的弹射阈值的因子;弹射阈值=均值-(因子*平均成功率标准差);不过，此处设置的值 需要除以1000以得到因子，例如，需要使用1.3为因子时，需要将该参数值设定为1300;
		consecutive_gateway_failure: ... # 因连续网关故障而弹出主机的最少连续故障数，默认为5;
		enforcing_consecutive_gateway_failure: ... # 基于连续网关故障检测到异常状态时而弹出主机的几率的百分比，默认为0; 
		split_external_local_origin_errors: ... # 是否区分本地原因而导致的故障和外部故障，默认为false;此项设置为true时，以下三项方能生效; 
		consecutive_local_origin_failure: ... # 因本地原因的故障而弹出主机的最少故障次数，默认为5; 
		enforcing_consecutive_local_origin_failure: ... # 基于连续的本地故障检测到异常状态而弹出主机的几率百分比，默认为100; 
		enforcing_local_origin_success_rate: ... # 基于本地故障检测的成功率统计检测到异常状态而弹出主机的几率，默认为100;
 

consecutive_5xx: "3" 
base_ejection_time: "30s"

consecutive_gateway_failure: "3" 
base_ejection_time: "30s" 
enforcing_consecutive_gateway_failure: "10"

interval: "10s"
base_ejection_time: "30s"
success_rate_minimum_hosts: "10"
success_rate_request_volume: "500"
success_rate_stdev_factor: "1000" # divided by 1000 to get a double

root@istio:~/ServiceMesh_in_Practise/cluster-manager/outlier-detection# ls
docker-compose.yaml  front-envoy.yaml

clusters:
- name: ...
	...
	load_assignment: {...}
		cluster_name: ...
		endpoints: [] # LocalityLbEndpoints列表，每个列表项主要由位置、端点列表、权重和优先级四项组成; 
		- locality: {...} # 位置定义
				region: ... 
				zone: ... 
				sub_zone: ...
			lb_endpoints: [] # 端点列表 
			- endpoint: {...} # 端点定义
					address: {...} # 端点地址
					health_check_config: {...} # 当前端点与健康状态检查相关的配置;
				load_balancing_weight: ... # 当前端点的负载均衡权重，可选;
				metadata: {...} # 基于匹配的侦听器、过滤器链、路由和端点等为过滤器提供额外信息的元数据，常用用于提供服务配置或辅助负载均衡; 
				health_status: ... # 端点是经EDS发现时，此配置项用于管理式设定端点的健康状态，可用值有UNKOWN、HEALTHY、UNHEALTHY、DRAINING、TIMEOUT和DEGRADED;
			load_balancing_weight: {...} 	# 设置locality权重
			priority: ... 								# 设置locality优先级
		policy: {...} # 负载均衡策略设定
			drop_overloads: [] 					# 过载保护机制，丢弃过载流量的机制;
			overprovisioning_factor: ... # 整数值，定义超配因子(百分比)，默认值为140，即1.4;
			endpoint_stale_after: ... 	# 过期时长，过期之前未收到任何新流量分配的端点将被视为过时，并标记为不健康;默认值0表示永不过时;
	lb_subset_config: {...} 
	ring_hash_lb_config: {...} 
	original_dst_lb_config: {...} 
	least_request_lb_config: {...} 
	common_lb_config: {...}
		health_panic_threshold: ... 					# Panic阈值，默认为50%;
		zone_aware_lb_config: {...} 					# 区域感知路由的相关配置;
		locality_weighted_lb_config: {...} 		# 局部权重负载均衡相关的配置;
		ignore_new_hosts_until_first_hc: ... 	# 是否在新加入的主机经历第一次健康状态检查之前不予考虑进负载均衡;
 

root@istio:~/ServiceMesh_in_Practise/cluster-manager/weighted-rr# ls
docker-compose.yaml  front-envoy.yaml  send-request.sh

least_request_lb_config:
	choice_count: "{...}" # 从健康主机中随机挑选出多少个做为样本进行最少连接数比较，默认为2;

ring_hash_lb_config:
	"minimum_ring_size": "{...}", # 哈希环的最小值，环越大调度结果越接近权重酷比，默认为1024，最在值为8M; 
	"hash_function": "...", # 哈希算法，支持XX_HASH和MURMUR_HASH_2两种，默认为前一种; 
	"maximum_ring_size": "{...}" # 哈希环的最大值，默认为8M;不过，值越大越消耗计算资源;

route_config:
	...
	virutal_host:s: 
	- ...
		routes:
		- match:
				...
			route:
				...
				hash_policy: [] # 指定哈希策略列表，每个列表项仅可设置如下header、cookie或connection_properties三者之一;
					header: {...}
						header_name: ... # 要哈希的首部名称
					cookie: {...}
						name: ... # cookie的名称，其值将用于哈希计算，必选项;
						ttl: ... # 持续时长，不存在带有ttl的cookie将自动生成该cookie;如果TTL存在且为零，则生成的cookie将是会话cookie 
						path: ... # cookie的路径;
					connection_properties: {...}
						source_ip: ... # 布尔型值，是否哈希源IP地址;
					terminal: ... # 是否启用哈希算法的短路标志，即一旦当前策略生成哈希值，将不再考虑列表中后续的其它哈希策略;

static_resources:
  listeners:
  - address:
      socket_address:
        address: 0.0.0.0
        port_value: 80
    name: listener_http
    filter_chains:
    - filters:
      - name: envoy.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.config.filter.network.http_connection_manager.v2.HttpConnectionManager
          codec_type: auto
          stat_prefix: ingress_http
          route_config:
            name: local_route
            virtual_hosts:
            - name: backend
              domains:
              - "*"
              routes:
              - match:
                  prefix: "/"
                route:
                  cluster: webcluster1
                  hash_policy:  #基于head的hash
                  - header:
                      header_name: User-Agent
          http_filters:
          - name: envoy.router

  clusters:
  - name: webcluster1
    connect_timeout: 0.25s
    type: STRICT_DNS
    lb_policy: RING_HASH  #hash环
    ring_hash_lb_config:  #hash环配置
      maximum_ring_size: 1048576
      minimum_ring_size: 512
    http2_protocol_options: {}
    load_assignment:
      cluster_name: webcluster1
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: myservice
                port_value: 80

root@istio:~/ServiceMesh_in_Practise/cluster-manager/ring-hash# ls
docker-compose.yaml  front-envoy.yaml

# endpoint.LocalityLbEndpoints

{
	"locality": "{...}", 
	"lb_endpoints": [], 
	"load_balancing_weight": "{...}", 
	"priority": "..."
} 

# Cluster.CommonLbConfig
{
	"healthy_panic_threshold": "{...}", # 百分比数值，定义恐慌阈值，默认为50%; 
	"zone_aware_lb_config": "{...}",
	"locality_weighted_lb_config": "{...}",
	"update_merge_window": "{...}",
	"ignore_new_hosts_until_first_hc": "..."
}

clusters:
- name: webcluster1
	connect_timeout: 0.25s 
	type: STRICT_DNS 
	lb_policy: ROUND_ROBIN 
	load_assignment:
		cluster_name: webcluster1 
		endpoints: #定义了2个locality。默认情况下由优先级高的locality下的端点使用lb_policy: ROUND_ROBIN的方式处理
		- locality:
				region: cn-north-1
			priority: 0 
			lb_endpoints:
			- endpoint:
					address:
						socket_address:
							address: colored
							port_value: 80
		- locality:  #当基于主动健康检测时，高优先级的locality中的ep不健康后，并且不健康的比例超过了超配因子(即(100-健康比例*超配因子)>0)后，会将(100-健康比例*超配因子)%该比例的流量导向该locality
				region: cn-north-2
			priority: 1 
			lb_endpoints:
			- endpoint:
					address:
						socket_address:
							address: myservice
							port_value: 80
	health_checks:
	- ...

root@istio:~/ServiceMesh_in_Practise/cluster-manager/priority-levels# ls
README.md  docker-compose.yaml  front-envoy.yaml

cluster:
- name: ...
	...
	common_lb_config:
		locality_weighted_lb_config: {} # 启用位置加权负载均衡机制，它没有可用的子参数;
		...
	load_assignment:
		endpoints:
			locality: "{...}"
			lb_endpoints": []
			load_balancing_weight: "{}" # 整数值，定义当前位置或优先级的权重，最小值为1; 
			priority: "..."

health(L_X) = 140 * healthy_X_backends / total_X_backends 
effective_weight(L_X) = locality_weight_X * min(100, health(L_X)) 
load to L_X = effective_weight(L_X) / Σ_c(effective_weight(L_c))

clusters:
- name: webcluster1
	connect_timeout: 0.25s 
	type: STRICT_DNS 
	lb_policy: ROUND_ROBIN 
	common_lb_config:
		locality_weighted_lb_config: {}  #启用“位置权重”
	load_assignment:
		cluster_name: webcluster1 
		policy:
			overprovisioning_factor: 140
		endpoints:
		- locality:
				region: cn-north-1
			priority: 0   #locality的优先级
			load_balancing_weight: 1   #locality的权重(位置权重)
			lb_endpoints:
			- endpoint:
					address:
						socket_address:
						address: colored
						port_value: 80
		- locality:
				region: cn-north-2
			priority: 0   #locality的优先级
			load_balancing_weight: 2    #locality的权重
			lb_endpoints:
			- endpoint:
					address:
						socket_address:
						address: myservice
						port_value: 80					

root@istio:~/ServiceMesh_in_Practise/cluster-manager/locality-weighted# ls
README.md  docker-compose.yaml  front-envoy.yaml  send-request.sh

load_assignment:
	cluster_name: webcluster1 
	endpoints:
	- lb_endpoints:
		- endpoint:
				address:
					socket_address:
						protocol: TCP 
						address: ep1 
						port_value: 80
		  metadata:
				filter_metadata:
					envoy.lb:
						version: '1.0'
						stage: 'prod'

clusters:
- name ...
	...
	lb_subset_config
		fallback_policy: "..." # 回退策略，默认为NO_FALLBACK 
		default_subset: "{...}" # 回退策略DEFAULT_SUBSET使用的默认子集; 
		subset_selectors: [] 	# 子集选择器
		- keys: [] 								# 定义一个选择器，指定用于归类主机元数据的键列表;
			- key1
			- key2
			- ...
			fallback_policy: ... 		# 当前选择器专用的回退策略;
		locality_weight_aware: "..." # 是否在将请求路由到子集时考虑端点的位置和位置权重;存在一些潜在的缺陷; 	
		scale_locality_weight: "..." # 是否将子集与主机中的主机比率来缩放每个位置的权重;
		panic_mode_any: "..." 	# 是否在配置回退策略且其相应的子集无法找到主机时尝试从整个集群中选择主机; 
		list_as_any: "..."

routes:
- name: ...
	match: {...}
	route: {...} # 路由目标，cluster和weighted_clusters只能使用其一;
		cluster:
		metadata_match: {...} # 子集负载均衡器使用的端点元数据匹配条件;若使用了weighted_clusters且内部定义了metadat_match，
													# 则元数据将被合并，且weighted_cluster中定义的值优先;过滤器名称应指定为envoy.lb;
			filter_metadata: {...} # 元数据过滤器
				envoy.lb: {...}
					key1: value1 
					key2: value2 
					...
		weighted_clusters: {...}
			clusters: []
			- name: ...
				weight: ... 
				metadata_match: {...}

    lb_subset_config:
      fallback_policy: DEFAULT_SUBSET
      default_subset:
        stage: "prod"
        version: "1.0"
        type: "std"
      subset_selectors:
      - keys: ["stage", "type"]
      - keys: ["stage", "version"]
      - keys: ["version"]
      - keys: ["xlarge", "version"]

              routes:
              - match:
                  prefix: "/"
                  headers:
                  - name: x-custom-version
                    value: pre-release
                route:
                  cluster: webcluster1
                  metadata_match:
                    filter_metadata:
                      envoy.lb:
                        version: "1.2-pre"
                        stage: "dev"
              - match:
                  prefix: "/"
                  headers:
                  - name: x-hardware-test
                    value: memory
                route:
                  cluster: webcluster1
                  metadata_match:
                    filter_metadata:
                      envoy.lb:
                        type: "bigmem"
                        stage: "prod"
              - match:
                  prefix: "/"
                route:
                  weighted_clusters:
                    clusters:
                    - name: webcluster1
                      weight: 90
                      metadata_match:
                        filter_metadata:
                          envoy.lb:
                            version: "1.0"
                    - name: webcluster1
                      weight: 10
                      metadata_match:
                        filter_metadata:
                          envoy.lb:
                            version: "1.1"
                  metadata_match:
                    filter_metadata:
                      envoy.lb:
                        stage: "prod"

root@istio:~/ServiceMesh_in_Practise/cluster-manager/lb-subsets# ls
README.md  docker-compose.yaml  front-envoy.yaml  test.sh

clusters:
- name: ...
	...
	connect_timeout: ... # TCP连接的超时时长，即主机网络连接超时，合理的设置可以能够改善因调用服务变慢而导致整个链接变慢的情形; 
	max_requests_per_connection: ... # 每个连接可以承载的最大请求数，HTTP/1.1和HTTP/2的连接池均受限于此设置，无设置则无限制，1表示禁用keep-alive 
	...
	circuit_breakers: {...} # 熔断相关的配置，可选;
		threasholds: [] # 适用于特定路由优先级的相关指标及阈值的列表; 
		- priority: ... # 当前断路器适用的路由优先级;
			max_connections: ... # 上游集群可承载的最大连接数，默认为1024;
			max_pending_requests: ... # 上游集群支持的可挂起的最大请求数，默认为1024;
			max_requests: ... # Envoy可调度给上游集群的最大并发请求数，默认为1024;
			max_retries: ... # 允许发往上游集群的最大并发重试数量，默认为3;
			track_remaining: ... # 其值为true时表示将公布统计数据以显示断路器打开前所剩余的资源数量;默认为false; 
			max_connection_pools: ... # 每个集群可同时打开的最大连接池数量，默认为无限制;

clusters:
- name: service_httpbin
	connect_timeout: 2s
	type: LOGICAL_DNS 
	dns_lookup_family: V4_ONLY
	lb_policy: ROUND_ROBIN 
	load_assignment:
		cluster_name: service_httpbin 
		endpoints:
		- lb_endpoints:
			- endpoint:
					address:
						socket_address:
							address: httpbin.org 
							port_value: 80
	circuit_breakers:
		thresholds:
			max_connections: 1 
			max_pending_requests: 1 
			max_retries: 3 
			max_requests: 1

root@istio:~/ServiceMesh_in_Practise/cluster-manager/circuit-breaker# ls
docker-compose.yaml  front-envoy.yaml  send-requests.sh  service-envoy.yaml