@@ -40,8 +40,8 @@ Items marked with (R) are required *prior to targeting to a milestone / release*
40
40
- [x] (R) Graduation criteria is in place
41
41
- [x] (R) Production readiness review completed
42
42
- [x] (R) Production readiness review approved
43
- - [ ] "Implementation History" section is up-to-date for milestone
44
- - [ ] User-facing documentation has been created in [ kubernetes/website] , for publication to [ kubernetes.io]
43
+ - [x ] "Implementation History" section is up-to-date for milestone
44
+ - [x ] User-facing documentation has been created in [ kubernetes/website] , for publication to [ kubernetes.io]
45
45
- [ ] Supporting documentation—e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes
46
46
47
47
## Summary
@@ -194,7 +194,9 @@ See unit tests above.
194
194
### Monitoring Requirements
195
195
196
196
* ** How can an operator determine if the feature is in use by workloads?**
197
- N/A
197
+ Users can check if the ` Scope ` and ` Namespace ` fields are set on IngressClass
198
+ resources. These fields being set do not guarantee that the controller responsible
199
+ for the class is using them or not.
198
200
199
201
* ** What are the SLIs (Service Level Indicators) an operator can use to
200
202
determine the health of the service?**
@@ -251,6 +253,8 @@ See unit tests above.
251
253
## Implementation History
252
254
253
255
- January 28, 2021: KEP written
256
+ - March 6, 2020: [ PR] ( https://github.com/kubernetes/kubernetes/pull/99275 ) adding
257
+ the feature merged in alpha state in v1.21
254
258
255
259
## Drawbacks
256
260
@@ -264,4 +268,4 @@ scoped and cluster scoped resources.
264
268
implementation.
265
269
266
270
- We could not support namespace-scoped parameters references. This would be
267
- simplest but would rule out some compelling use cases.
271
+ simplest but would rule out some compelling use cases.
0 commit comments