fix: allow kubelet to be started via the API

In addition to restart action, allow also start action. If the service fails to start, it transitions to `Failed` state and it should be actually started to bring it back to running state. Fixes #4665 Also GC'ed now unused condition (it had been used before kubelet started being controlled via COSI). Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com> (cherry picked from commit ab42886)
siderolabs · Dec 13, 2021 · 02796f8 · 02796f8
1 parent e69eaca
commit 02796f8
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 147 deletions.
diff --git a/internal/app/machined/pkg/system/services/kubelet.go b/internal/app/machined/pkg/system/services/kubelet.go
@@ -203,6 +203,11 @@ func (k *Kubelet) APIRestartAllowed(runtime.Runtime) bool {
 	return true
 }
 
+// APIStartAllowed implements APIStartableService.
+func (k *Kubelet) APIStartAllowed(runtime.Runtime) bool {
+	return true
+}
+
 func kubeletSeccomp(seccomp *specs.LinuxSeccomp) {
 	// for cephfs mounts
 	seccomp.Syscalls = append(seccomp.Syscalls,

diff --git a/pkg/machinery/resources/k8s/condition.go b/pkg/machinery/resources/k8s/condition.go
diff --git a/pkg/machinery/resources/k8s/condition_test.go b/pkg/machinery/resources/k8s/condition_test.go