Change:
apiserverCurrentInqueueRequests = compbasemetrics.NewGaugeVec( &compbasemetrics.GaugeOpts{ <del> Namespace: namespace, Subsystem: subsystem, Name:      "current_inqueue_requests", Help:      "Number of requests currently pending in queues of the API Priority and Fairness system", </del> <ins> Namespace:      namespace, Subsystem:      subsystem, Name:           "current_inqueue_requests", Help:           "Number of requests currently pending in queues of the API Priority and Fairness system", StabilityLevel: compbasemetrics.ALPHA, </ins> }, []string{priorityLevel, flowSchema}, ) apiserverRequestQueueLength = compbasemetrics.NewHistogramVec( &compbasemetrics.HistogramOpts{ <del> Namespace: namespace, Subsystem: subsystem, Name:      "request_queue_length_after_enqueue", Help:      "Length of queue in the API Priority and Fairness system, as seen by each request after it is enqueued", Buckets:   queueLengthBuckets, </del> <ins> Namespace:      namespace, Subsystem:      subsystem, Name:           "request_queue_length_after_enqueue", Help:           "Length of queue in the API Priority and Fairness system, as seen by each request after it is enqueued", Buckets:        queueLengthBuckets, StabilityLevel: compbasemetrics.ALPHA, </ins> }, []string{priorityLevel, flowSchema}, ) apiserverRequestConcurrencyLimit = compbasemetrics.NewGaugeVec( &compbasemetrics.GaugeOpts{ <del> Namespace: namespace, Subsystem: subsystem, Name:      "request_concurrency_limit", Help:      "Shared concurrency limit in the API Priority and Fairness system", </del> <ins> Namespace:      namespace, Subsystem:      subsystem, Name:           "request_concurrency_limit", Help:           "Shared concurrency limit in the API Priority and Fairness system", StabilityLevel: compbasemetrics.ALPHA, </ins> }, []string{priorityLevel}, ) apiserverCurrentExecutingRequests = compbasemetrics.NewGaugeVec( &compbasemetrics.GaugeOpts{ <del> Namespace: namespace, Subsystem: subsystem, Name:      "current_executing_requests", Help:      "Number of requests currently executing in the API Priority and Fairness system", </del> <ins> Namespace:      namespace, Subsystem:      subsystem, Name:           "current_executing_requests", Help:           "Number of requests currently executing in the API Priority and Fairness system", StabilityLevel: compbasemetrics.ALPHA, </ins> }, []string{priorityLevel, flowSchema}, ) apiserverRequestWaitingSeconds = compbasemetrics.NewHistogramVec( &compbasemetrics.HistogramOpts{ <del> Namespace: namespace, Subsystem: subsystem, Name:      "request_wait_duration_seconds", Help:      "Length of time a request spent waiting in its queue", Buckets:   requestDurationSecondsBuckets, </del> <ins> Namespace:      namespace, Subsystem:      subsystem, Name:           "request_wait_duration_seconds", Help:           "Length of time a request spent waiting in its queue", Buckets:        requestDurationSecondsBuckets, StabilityLevel: compbasemetrics.ALPHA, </ins> }, []string{priorityLevel, flowSchema, "execute"}, ) apiserverRequestExecutionSeconds = compbasemetrics.NewHistogramVec( &compbasemetrics.HistogramOpts{ <del> Namespace: namespace, Subsystem: subsystem, Name:      "request_execution_seconds", Help:      "Duration of request execution in the API Priority and Fairness system", Buckets:   requestDurationSecondsBuckets, </del> <ins> Namespace:      namespace, Subsystem:      subsystem, Name:           "request_execution_seconds", Help:           "Duration of request execution in the API Priority and Fairness system", Buckets:        requestDurationSecondsBuckets, StabilityLevel: compbasemetrics.ALPHA, </ins> }, []string{priorityLevel, flowSchema}, )

Discussion:
<!-- Please only use this template for submitting enhancement requests --What would you like to be : API priority and fairness metrics have labels such as "priorityLevel" and "flowSchema". These should be "prioritylevel" and "flowschema" respectively. These metrics have been to an exception list: Why is this needed: snake_case is consistent with other metrics. /sig api-machinery /kind cleanup /cc Do we want to do this before 1.20 beta?
yes, lets do that.
/triage accepted Yes, we do not want to go to beta with known wrongness in the metrics.