From 008dc87aa9b9eb9ae130e424073b03cd6cf2edd2 Mon Sep 17 00:00:00 2001 From: helen Date: Sun, 2 Oct 2022 18:54:54 +0800 Subject: [PATCH] Remove HTTP Server support for pushing pods onto the kubelet #3015 Signed-off-by: helen Signed-off-by: helen --- cmd/kubelet/app/server.go | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/cmd/kubelet/app/server.go b/cmd/kubelet/app/server.go index c8a67942b17..a9cb66aaf31 100644 --- a/cmd/kubelet/app/server.go +++ b/cmd/kubelet/app/server.go @@ -144,7 +144,7 @@ various mechanisms (primarily through the apiserver) and ensures that the contai described in those PodSpecs are running and healthy. The kubelet doesn't manage containers which were not created by Kubernetes. -Other than from an PodSpec from the apiserver, there are three ways that a container +Other than from an PodSpec from the apiserver, there are two ways that a container manifest can be provided to the Kubelet. File: Path passed as a flag on the command line. Files under this path will be monitored @@ -152,10 +152,7 @@ periodically for updates. The monitoring period is 20s by default and is configu via a flag. HTTP endpoint: HTTP endpoint passed as a parameter on the command line. This endpoint -is checked every 20 seconds (also configurable with a flag). - -HTTP server: The kubelet can also listen for HTTP and respond to a simple API -(underspec'd currently) to submit a new manifest.`, +is checked every 20 seconds (also configurable with a flag).`, // The Kubelet has special flag parsing requirements to enforce flag precedence rules, // so we do all our parsing manually in Run, below. // DisableFlagParsing=true provides the full set of flags passed to the kubelet in the