kubelet: Allow runonce mode to contact apiserver #23074
Conversation
This patch allows a kubelet to contact an apiserver and use that as a pod source in runonce mode. This "non-standalone" mode will cause the kubelet to register with an apiserver, ignore "source ready" pod updates, and run the first pod received from the apiserver before exiting. As during a typical "non-standalone" kubelet, the runonce kubelet will update the apiserver with the status of the pod it has ran. Additionally, a new flag has been added: `--runonce-timeout`, which allows the user to configure the timeout for a kubelet in runonce mode, as opposed to hard coding it. The default flag value is the same as what the hard coded value previously was. Fixes kubernetes#23073
|
Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist") This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
1 similar comment
|
Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist") This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
k8s-github-robot
added
kind/old-docs
size/M
|
Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist") This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry. Otherwise, if this message is too spammy, please complain to ixdy. |
|
@derekparker PR needs rebase |
k8s-github-robot
added
needs-rebase
|
Closing in favor of #25596 |
This patch allows a kubelet to contact an apiserver and use
that as a pod source in runonce mode. This "non-standalone" mode will
cause the kubelet to register with an apiserver, ignore "source ready"
pod updates, and run the first pod received from the apiserver before
exiting. As during a typical "non-standalone" kubelet, the runonce
kubelet will update the apiserver with the status of the pod it has ran.
Additionally, a new flag has been added:
--runonce-timeout, whichallows the user to configure the timeout for a kubelet in runonce mode,
as opposed to hard coding it. The default flag value is the same as what
the hard coded value previously was.
Fixes #23073