1. Proposed title of this feature request

Option to set up --goaway-chance flag for kube apiserver into OCP. It is documented in the upsteam kubernetes docs here https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/

2. What is the nature and description of the request?

Supported way to deploy --goaway-chance fag we need to modify unsupportedConfigOverrides, this should be doable without modifying the unsupportedConfigOverrides which violates support. That means two things  A) come up with a way (likely a configmap) where the option can be set and B) test with that option turned on

3. Why does the customer need this? (List the business requirements here)

Given the nature of http/2 connections on large clusters, connection streams reuse the old connection which stresses one kube apiserver pod and causes instability to the cluster, with this option, kube apiserver will terminate a few connections gracefully and choose a different target kube apiserver pod hence bringing more stability to these large cluste

4. List any affected packages or components.

kube-apiserver packages in OpenShift Container platform