Remove deprecated --container-runtime flag from kubelet config.

The flag has been removed in k8s v1.27; I verified removing this flag works not only with k8s v1.27, but also v1.24 -> v1.26. Signed-off-by: Cesar Talledo <cesar.talledo@docker.com>
nestybox · Aug 15, 2023 · 7c9a3d8 · 7c9a3d8
1 parent ffe0e86
commit 7c9a3d8
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 2 deletions.
diff --git a/k8s/config/crio-kubelet-options b/k8s/config/crio-kubelet-options
@@ -1,4 +1,3 @@
---container-runtime=remote
 --container-runtime-endpoint=unix:///var/run/crio/crio.sock
 --image-service-endpoint=unix:///var/run/crio/crio.sock
 --runtime-cgroups=/system.slice/crio.service

diff --git a/k8s/scripts/sysbox-deploy-k8s.sh b/k8s/scripts/sysbox-deploy-k8s.sh
@@ -1045,7 +1045,7 @@ function main() {
 
 		# Switch the K8s runtime to CRI-O
 		#
-		# Note: this will configure the Kubelet to use CRI-O and restart it;,
+		# Note: this will configure the Kubelet to use CRI-O and restart it,
 		# thereby killing all pods on the K8s node (including this daemonset).
 		# The K8s control plane will then re-create the pods, but this time
 		# with CRI-O. The operation can take up to 1 minute.