@@ -191,10 +191,10 @@ configured. Here are some examples:
191
191
The ` /var/log/ ` endpoint is enabled using the ` enableSystemLogHandler ` kubelet
192
192
configuration options. To gain access to this new feature this option needs to
193
193
be enabled. In addition when introducing this feature it will be hidden behind a
194
- ` NodeLogs ` feature gate in the kubelet that needs to be explicitly enabled. So
194
+ ` NodeLogViewer ` feature gate in the kubelet that needs to be explicitly enabled. So
195
195
you need to enable both options to get access to this new feature and disabling
196
196
` enableSystemLogHandler ` will disable the new feature irrespective of the
197
- ` NodeLogs ` feature gate.
197
+ ` NodeLogViewer ` feature gate.
198
198
199
199
A reference implementation of this feature without the feature gate is
200
200
available [ here] ( https://github.com/kubernetes/kubernetes/pull/96120 ) .
@@ -260,12 +260,12 @@ have been added. A reference implementation of the tests can be seen
260
260
261
261
### Graduation Criteria
262
262
263
- The plan is to introduce the feature as alpha in the v1.22 time frame behind the
263
+ The plan is to introduce the feature as alpha in the v1.25 time frame behind the
264
264
` NodeLogs ` feature gate.
265
265
266
266
#### Alpha -> Beta Graduation
267
267
268
- The plan is to graduate the feature to beta in the v1.23 time frame. At that
268
+ The plan is to graduate the feature to beta in the v1.26 time frame. At that
269
269
point we would have collected feedback from cluster administrators and
270
270
developers who have enabled the feature. Based on this feedback and issues
271
271
opened we should consider adding a kubelet side throttle for the viewing the
@@ -275,7 +275,7 @@ between file vs journal / WinEvent logs.
275
275
276
276
#### Beta -> GA Graduation
277
277
278
- The plan is to graduate the feature to GA in the v1.24 time frame at which point
278
+ The plan is to graduate the feature to GA in the v1.27 time frame at which point
279
279
any major issues should have been surfaced and addressed during the alpha and
280
280
beta phases.
281
281
@@ -293,13 +293,13 @@ viewer, the result should be "feature not supported".
293
293
294
294
* ** How can this feature be enabled / disabled in a live cluster?**
295
295
- [x] Feature gate
296
- - Feature gate name: NodeLogs
296
+ - Feature gate name: NodeLogViewer
297
297
- Components depending on the feature gate: kubelet
298
298
299
299
* ** Does enabling the feature change any default behavior?** No
300
300
301
301
* ** Can the feature be disabled once it has been enabled (i.e. can we roll back
302
- the enablement)?** Yes. It can be disabled by disabling the ` NodeLogs ` feature
302
+ the enablement)?** Yes. It can be disabled by disabling the ` NodeLogViewer ` feature
303
303
gate in the kubelet.
304
304
305
305
* ** What happens if we reenable the feature if it was previously rolled back?**
0 commit comments