istio-api: deprecate consecutive_errors and add gateway & 5xx errors

With the original consecutive_errors design, there is no way to turn
off consecutive gateway errors. This CL deprecate the field and add two
new fields: consecutive_gateway_errors and consecutive_5xx_errors.

See discussions here: #909

Change-Id: I0e98990d194216cef842fb792a76a5f59b6e674e
Reviewed-on: https://gerrit.musta.ch/c/public/istio-api/+/199
Reviewed-by: Jungho Ahn <[email protected]>
Reviewed-by: Weibo He <[email protected]>

Author: yingzhuivy

kubernetes/customresourcedefinitions.gen.yaml

@@ -135,9 +135,20 @@
             "type": "string"
           },
           "consecutiveErrors": {
-            "description": "Number of errors before a host is ejected from the connection pool. Defaults to 5. When the upstream host is accessed over HTTP, a 502, 503, or 504 return code qualifies as an error. When the upstream host is accessed over an opaque TCP connection, connect timeouts and connection error/failure events qualify as an error.",
+            "description": "Number of errors before a host is ejected from the connection pool. Defaults to 5. When the upstream host is accessed over HTTP, a 502, 503, or 504 return code qualifies as an error. When the upstream host is accessed over an opaque TCP connection, connect timeouts and connection error/failure events qualify as an error. $hide_from_docs",
             "type": "integer",
-            "format": "int32"
+            "format": "int32",
+            "deprecated": true
+          },
+          "consecutiveGatewayErrors": {
+            "description": "Number of gateway errors before a host is ejected from the connection pool. When the upstream host is accessed over HTTP, a 502, 503, or 504 return code qualifies as an error. When the upstream host is accessed over an opaque TCP connection, connect timeouts and connection error/failure events qualify as a gateway error. If set to 0, this feature is disabled. Defaults to 5.",
+            "type": "integer",
+            "nullable": true
+          },
+          "consecutive5xxErrors": {
+            "description": "Number of 5xx errors before a host is ejected from the connection pool. When the upstream host is accessed over TCP, errors are internally mapped to HTTP 5xx codes and treated as such. If set to 0, this feature is disabled. Defaults to 0. consecutive_gateway_errors and consecutive_5xx_errors can be used separately or together. The errors counted by consecutive_gateway_errors are also included in consecutive_5xx_errors, so consecutive_gateway_errors should be less than consecutive_5xx_errors when both are used.",
+            "type": "integer",
+            "nullable": true
           },
           "baseEjectionTime": {
             "description": "Minimum ejection duration. A host will remain ejected for a period equal to the product of minimum ejection duration and the number of times the host has been ejected. This technique allows the system to automatically increase the ejection period for unhealthy upstream servers. format: 1h/1m/1s/1ms. MUST BE \u003e=1ms. Default is 30s.",