developer-productivity

/area API
/area autoscale
/kind cleanup

Actual Behavior

The max-scale and min-scale annotation has been introduced in knative/serving#12103 alignment. The client was using those names, but recently this changed to the inverse - knative/client#958. This leads to confusion on docs, and UX as seen in: https://github.com/knative/docs/iss

Problem

I'm getting this warning on k8s 1.23:

Warning: policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget

on

Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.0", GitCommit:"c2b5237ccd9c0f1d600d3072634ca66cefdf272f", GitTreeState:"clean", BuildDate:"2021-08-04T18:03:20Z", GoVersion:"go1.1

Describe the bug
In DORA dashboards, for the top left gauge chart Weekly Release / Deployment Frequency (Avg), we use a UI built query to compute the average. It is incorrect because weeks with no releases / deployments are simply ignored in the final averaging because of how the query is built. Indeed, the first aggregation that counts per week will have no entries for week with no release /

Add a toggle either global near the search or individually on snippet components.

• Global may be preferable to not clutter up the UI with a toggle on each snippet
• Or, when in full dashboard or a folder with many snippets, it may be inconvenient to scroll back to the top to enable it
• Could also be a preference in the profile