apiVersion: release-notes/v2
kind: feature
area: traffic-management

releaseNotes:
- |
  **Added** warning validation messages when a DestinationRule specifies failover policies but does not provide an OutlierDetection policy.

Zhonghu Xu <******@****.***> 1629874146 +0800

			},
			expectedLabels: nil,
		},
		{
			name: "no failover priority",
			dr: &config.Config{
				Spec: &networking.DestinationRule{
					TrafficPolicy: &networking.TrafficPolicy{
						OutlierDetection: &networking.OutlierDetection{
							ConsecutiveErrors: 5,
						},
					},
				},
			},
			expectedLabels: nil,
		},
		{
			name: "failover priority disabled",
			dr: &config.Config{

apiVersion: release-notes/v2
kind: feature
area: traffic-management
releaseNotes:
- |

				},
				{
					"Failover/CDS",
					LocalityInput{
						LocalitySetting: localityFailover,
						Resolution:      "DNS",
						Local:           "fake-should-fail.example.com",
						NearLocal:       destA.Config().Service,
						Remote:          destB.Config().Service,
					},
					expectAllTrafficTo(destA.Config().Service),
				},
				{
					"Failover/EDS",
					LocalityInput{

releaseNotes:
  - |
    **Added** The locality load balancing docs have been re-written into a
    formal traffic management task. The new docs describe in more detail
    how locality load balancing works as well as how to configure both
    failover and weighted distribution. In addition, the new docs are now

"portLevelSettings"
"labels"
"http"
"consecutiveGatewayErrors"
"consecutive5xxErrors"
"interval"
"baseEjectionTime"
"maxEjectionPercent"
"minHealthPercent"
"clientCertificate"
"sni"
"distribute"
"failover"
"enabled"
"httpHeaderName"
"httpCookie"
"useSourceIp"
"httpQueryParameterName"
"minimumRingSize"
"path"
"tcpKeepalive"
"http1MaxPendingRequests"
"http2MaxRequests"
"maxRequestsPerConnection"

Calls are executed in one of two ways:

 * **Synchronous:** your thread blocks until the response is readable.

	// +---v-------------v----^---------v------^---->
	//     t0           t1             t2
	//
	// We have the guarantees:
	// - in normal cases, the interval is 5 minutes.
	// - in failover, the interval is >5m and <10m
	//
	// FAQ:
	// - What if time is not accurate? We don't care as long as someone did the compaction. Atomicity is ensured using
	//   etcd API.