Skip to content

Commit 0a8d072

Browse files
committed
fixup! KEP-3221: update kep
Signed-off-by: Nabarun Pal <[email protected]>
1 parent bbaaa38 commit 0a8d072

File tree

1 file changed

+3
-3
lines changed
  • keps/sig-auth/3221-structured-authorization-configuration

1 file changed

+3
-3
lines changed

keps/sig-auth/3221-structured-authorization-configuration/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -631,18 +631,18 @@ Or, they can look at the metrics exposed by `kube-apiserver`.
631631
###### How can someone using this feature know that it is working for their instance?
632632

633633
- [x] Other
634-
- Details: They can look at the metrics if `apiserver_authorization_step_invocations_total` is increasing.
634+
- Details: They can look at the metrics if `apiserver_authorization_decisions_total` is increasing.
635635

636636
###### What are the reasonable SLOs (Service Level Objectives) for the enhancement?
637637

638-
The amount of errors denoted by `apiserver_authorization_step_webhook_error_total`
638+
The total number of `apiserver_authorization_step_webhook_error_total` metric with failure code
639639
is within reasonable limits. A rising value indicates issues with either the
640640
authorizer chain or the webhook itself.
641641

642642
###### What are the SLIs (Service Level Indicators) an operator can use to determine the health of the service?
643643

644644
- [x] Metrics
645-
- Metric name: `apiserver_authorization_step_invocations_total`
645+
- Metric name: `apiserver_authorization_decisions_total`
646646
- Components exposing the metric: kube-apiserver
647647

648648
If the cluster administrator has defined an authorizer chain and the above metric

0 commit comments

Comments
 (0)