Skip to content

Commit f6fbf42

Browse files
Remove comments
1 parent e01b5c1 commit f6fbf42

File tree

1 file changed

+0
-24
lines changed

1 file changed

+0
-24
lines changed

keps/sig-apps/2214-indexed-job/README.md

Lines changed: 0 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -501,10 +501,6 @@ This feature has no node runtime implications.
501501

502502
### Feature Enablement and Rollback
503503

504-
<!--
505-
This section must be completed when targeting alpha to a release.
506-
-->
507-
508504
###### How can this feature be enabled / disabled in a live cluster?
509505

510506

@@ -534,10 +530,6 @@ This section must be completed when targeting alpha to a release.
534530

535531
### Rollout, Upgrade and Rollback Planning
536532

537-
<!--
538-
This section must be completed when targeting beta to a release.
539-
-->
540-
541533
###### How can a rollout or rollback fail? Can it impact already running workloads?
542534

543535
If the new kube-controller-manager crashes, it's possible that an older
@@ -570,10 +562,6 @@ This section must be completed when targeting beta to a release.
570562

571563
### Monitoring Requirements
572564

573-
<!--
574-
This section must be completed when targeting beta to a release.
575-
-->
576-
577565
###### How can an operator determine if the feature is in use by workloads?
578566

579567
- job_sync_total has values for the label completion_mode=Indexed.
@@ -610,10 +598,6 @@ This section must be completed when targeting beta to a release.
610598

611599
### Dependencies
612600

613-
<!--
614-
This section must be completed when targeting beta to a release.
615-
-->
616-
617601
###### Does this feature depend on any specific services running in the cluster?
618602

619603
No, the feature only involves kube-apiserver and kube-controller-manager.
@@ -670,14 +654,6 @@ previous answers based on experience in the field.
670654

671655
### Troubleshooting
672656

673-
<!--
674-
This section must be completed when targeting beta to a release.
675-
676-
The Troubleshooting section currently serves the `Playbook` role. We may consider
677-
splitting it into a dedicated `Playbook` document (potentially with some monitoring
678-
details). For now, we leave it here.
679-
-->
680-
681657
###### How does this feature react if the API server and/or etcd is unavailable?
682658

683659
The job controller can't create or delete pods nor update job status.

0 commit comments

Comments
 (0)