Skip to content

Commit 66b4a54

Browse files
committed
WIP
1 parent ad504dc commit 66b4a54

File tree

2 files changed

+19
-7
lines changed

2 files changed

+19
-7
lines changed

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

Lines changed: 13 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -481,7 +481,7 @@ total invocation counts across the following labels.
481481
- `name`
482482
- `code` {"incomplete_request", "bad_response"}
483483

484-
3. `apiserver_authorization_webhook_evaluations_duration_seconds`
484+
3. `apiserver_authorization_webhook_duration_seconds`
485485

486486
This is a Histogram metric that will track the total round trip time of the requests to the webhook.
487487

@@ -499,10 +499,15 @@ Labels {along with possible values}:
499499
- `name`
500500
- `code` {"incomplete_request", "bad_response"}
501501

502-
5. `apiserver_authorization_configuration_reload_last_timestamp_seconds`
502+
5. `apiserver_authorization_config_controller_automatic_reload_last_timestamp_seconds`
503503

504-
This Gauge metric will record last time in seconds when an authorization reload was performed.
505-
- `status` {success, fail}
504+
This Gauge metric will record last time in seconds when an authorization reload was performed, partitioned by apiserver_id_hash.
505+
- `apiserver_id_hash`
506+
507+
6. `apiserver_authorization_config_controller_automatic_reload_failures_total` and `apiserver_authorization_config_controller_automatic_reload_success_total`
508+
509+
These Counter metrics record the total number of reload successes and failures, partitioned by API server apiserver_id_hash.
510+
- `apiserver_id_hash`
506511

507512
### Test Plan
508513

@@ -644,7 +649,8 @@ Not applicable.
644649

645650
###### Were upgrade and rollback tested? Was the upgrade->downgrade->upgrade path tested?
646651

647-
TBD.
652+
No. There is no data stored for this feature which persists between upgrade / downgrade,
653+
or between enable / disable. The feature is purely an API server configuration option.
648654

649655
###### Is the rollout accompanied by any deprecations and/or removals of features, APIs, fields of API types, flags, etc.?
650656

@@ -820,7 +826,8 @@ For each of them, fill in the following information by copying the below templat
820826
- [x] 2023-06-15 - KEP Accepted as implementable
821827
- [x] 2023-07-05 - Implementation started
822828
- [x] 2023-09-27 - Update KEP according to actual state
823-
- [ ] 2023-12-DD First release (1.29) when feature available
829+
- [x] 2023-12-15 - First release (1.29) when feature available
830+
- [x] 2024-01-29 - Targeting beta in 1.30
824831

825832
## Drawbacks
826833

keps/sig-auth/3221-structured-authorization-configuration/kep.yaml

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,13 +15,18 @@ approvers:
1515
see-also:
1616
- https://github.com/kubernetes/kubernetes/issues/101762
1717
stage: alpha
18-
latest-milestone: "v1.29"
18+
latest-milestone: "v1.30"
1919
milestone:
2020
alpha: "v1.29"
21+
beta: "v1.30"
2122
# The following PRR answers are required at alpha release
2223
# List the feature gate name and the components for which it must be enabled
2324
feature-gates:
2425
- name: StructuredAuthorizationConfig
2526
components:
2627
- kube-apiserver
2728
disable-supported: true
29+
metrics:
30+
- apiserver_authorization_config_controller_automatic_reload_last_timestamp_seconds
31+
- apiserver_authorization_config_controller_automatic_reload_success_total{apiserver_id_hash}
32+
- apiserver_authorization_config_controller_automatic_reload_failures_total{apiserver_id_hash}

0 commit comments

Comments
 (0)