Goal

CI test adjustments andadditional error tracking to measure the appropriate rate of errors from kube-apiserver, e.g. periods of disruption and apiserver unavailability.  This characteristic has become more apparent since ResilientWatchCacheInitialization was enabled in kube/OCP.

Benefit Hypothesis:

What are the benefits (to Red Hat, eventually to customers, to the community, etc.)? Does it improve security, performance, supportability, etc? Why is work a priority?

We believe that the result of doing this work will help inform on quality of the kube-apiserver, it's availability throughout the cluster lifecyle, and improve our CI/component readiness data.

Resources

Add any resources (docs, slides, etc.) pertinent to the definition of the work. These might not be known until later. Update as necessary.

Responsibilities

Indicate which roles and/or teams will be responsible for contributing to the initiative and generally what they might be expected to do.

Success Criteria

Provide some examples of how we will know if we have achieved the goal. What can be measured to determine success? What observable actions/outcomes that can be seen to determine success? Specific, Measurable, Achievable, fits within the Time-box.

Results

Add results here once the Initiative is started. Recommend discussions & updates once per quarter in bullets.