You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: keps/sig-auth/2784-csr-duration/README.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -225,16 +225,25 @@ during version skews (discussed below).
225
225
#### GA
226
226
227
227
- Confirm with [cert-manager](https://github.com/jetstack/cert-manager/pull/3646) that the new functionality addresses their use case
228
+
+[cert-manager/cert-manager#4957](https://github.com/cert-manager/cert-manager/pull/4957) successfully added the use of the `spec.expirationSeconds` field
228
229
- Confirm with [pinniped](https://pinniped.dev) that the new functionality addresses their use case
230
+
+ The Pinniped maintainers confirmed via [vmware-tanzu/pinniped#1070](https://github.com/vmware-tanzu/pinniped/pull/1070)
231
+
that the `spec.expirationSeconds` field was sufficient for their use case
229
232
- Confirm that no other metrics are necessary
233
+
+ No other metrics have been identified by the maintainers or requested by external actors
230
234
- Wait one release after beta to allow bugs to be reported
235
+
+ No bugs were reported over a two release period with multiple external actors consuming the new API field
231
236
- Inform external signer implementations of the `spec.expirationSeconds` field
* Opened [smart-edge-open/edgeservices#37](https://github.com/smart-edge-open/edgeservices/issues/37) to inform the maintainers of the `spec.expirationSeconds` field
0 commit comments