A FailoverService creates a new hostname to which services can send requests. Requests will be routed based on a list of backing traffic targets ordered by decreasing priority. When outlier detection detects that a traffic target in the list is in an unhealthy state, requests sent to the FailoverService will be routed to the next healthy traffic target in the list. For each traffic target referenced in the FailoverService's BackingServices list, outlier detection must be configured using a TrafficPolicy. Currently this feature only supports Services backed by Istio.
Field
Type
Label
Description
hostname
string
The DNS name of the FailoverService. Must be unique within the service mesh instance since it is used as the hostname with which clients communicate.
The list of services backing the FailoverService, ordered by decreasing priority. All services must be backed by either the same service mesh instance or backed by service meshes that are grouped under a common VirtualMesh.
FailoverServiceSpec.BackingService
The traffic targets that comprise the FailoverService.
Protocol of the requests sent to the FailoverService, must be one of HTTP, HTTPS, GRPC, HTTP2, MONGO, TCP, TLS.
FailoverServiceStatus
Field
Type
Label
Description
observedGeneration
int64
The most recent generation observed in the the FailoverService metadata. If the observedGeneration does not match generation, the controller has not received the most recent version of this resource.
