Add note: kubelet manages only k8s containers. #30435
Merged
+3
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/cc @kubernetes/rh-cluster-infra @ingvagabund |
k8s-github-robot
added
size/XS
|
@johndmulhausen, do we need to open PR for docs or does https://github.com/kubernetes/kubernetes.github.io/blob/master/docs/admin/kubelet.md gets re-generated automatically? |
| @@ -101,7 +101,7 @@ func NewKubeletCommand() *cobra.Command { | |||
| node. The kubelet works in terms of a PodSpec. A PodSpec is a YAML or JSON object | |||
| that describes a pod. The kubelet takes a set of PodSpecs that are provided through | |||
| various mechanisms (primarily through the apiserver) and ensures that the containers | |||
| described in those PodSpecs are running and healthy. | |||
| described in those PodSpecs are running and healthy. The kubelet doesn't manage containers which were not created by Kubernetes. | |||
There was a problem hiding this comment.
Can you wrap this line to match the others?
bug 1328441 Bugzilla link https://bugzilla.redhat.com/show_bug.cgi?id=1328441
hodovska
force-pushed
the
1328441-non-k8scontainers
branch
from
f603c99 to
08945a9
Compare
|
GCE e2e build/test passed for commit 08945a9. |
|
LGTM |
dchen1107
added
the
lgtm
k8s-github-robot
removed
the
lgtm
sttts
added
release-note-none
|
Automatic merge from submit-queue |
mfojtik
pushed a commit
to mfojtik/kubernetes
that referenced
this pull request
Aug 17, 2016
…ainers Automatic merge from submit-queue Add note: kubelet manages only k8s containers. Kubelet wrote log when accesing container which was not created in k8s, what could confuse users. That's why we added note about it in documentation and lowered log level of the message to 5. Here is example of the message: ``` > Apr 19 11:50:32 openshift-114.lab.sjc.redhat.com atomic-openshift-node[9551]: I0419 11:50:32.194020 9600 docker.go:363] Docker Container: /tiny_babbage is not managed by kubelet. ``` bug 1328441 Bugzilla link https://bugzilla.redhat.com/show_bug.cgi?id=1328441
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Kubelet wrote log when accesing container which was not created in k8s, what could confuse users. That's why we added note about it in documentation and lowered log level of the message to 5.
Here is example of the message:
bug 1328441
Bugzilla link https://bugzilla.redhat.com/show_bug.cgi?id=1328441
This change is