@@ -501,10 +501,6 @@ This feature has no node runtime implications.
501
501
502
502
# ## Feature Enablement and Rollback
503
503
504
- <!--
505
- This section must be completed when targeting alpha to a release.
506
- -->
507
-
508
504
# ##### How can this feature be enabled / disabled in a live cluster?
509
505
510
506
@@ -534,10 +530,6 @@ This section must be completed when targeting alpha to a release.
534
530
535
531
# ## Rollout, Upgrade and Rollback Planning
536
532
537
- <!--
538
- This section must be completed when targeting beta to a release.
539
- -->
540
-
541
533
# ##### How can a rollout or rollback fail? Can it impact already running workloads?
542
534
543
535
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.
570
562
571
563
# ## Monitoring Requirements
572
564
573
- <!--
574
- This section must be completed when targeting beta to a release.
575
- -->
576
-
577
565
# ##### How can an operator determine if the feature is in use by workloads?
578
566
579
567
- 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.
610
598
611
599
# ## Dependencies
612
600
613
- <!--
614
- This section must be completed when targeting beta to a release.
615
- -->
616
-
617
601
# ##### Does this feature depend on any specific services running in the cluster?
618
602
619
603
No, the feature only involves kube-apiserver and kube-controller-manager.
@@ -670,14 +654,6 @@ previous answers based on experience in the field.
670
654
671
655
# ## Troubleshooting
672
656
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
-
681
657
# ##### How does this feature react if the API server and/or etcd is unavailable?
682
658
683
659
The job controller can't create or delete pods nor update job status.
0 commit comments