Bug 1328441
| Summary: | Docker Container: * is not managed by kubelet. | ||
|---|---|---|---|
| Product: | OKD | Reporter: | Aleksandar Kostadinov <akostadi> |
| Component: | Pod | Assignee: | Jan Chaloupka <jchaloup> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Xiaoli Tian <xtian> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.x | CC: | akostadi, aos-bugs, jialiu, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-11-22 12:55:09 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Aleksandar Kostadinov
2016-04-19 11:55:37 UTC
This is a harmless message. It's just indicating that there are some Docker containers on the node that were not created by Kubernetes. This message is displayed at loglevel 3. We could consider lowering the level to something like 5 if that would be helpful. Ok, thank you. I don't have opinion about log level. Might be good to be documented if not done already. Reading openshift and kubernetes docs for a while. It looks like this behaviour is not documented anywhere or it is hard to find it. Aleksandar, would it be enough to document this behaviour? This is suitable for kubelet and his management of containers. Partially, garbage collector mentiones [1]: "Containers that are not managed by kubelet are not subject to container garbage collection." Nothing else so far. [1] http://kubernetes.io/docs/admin/garbage-collection/ Undirectly, it is state here [1]: "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." Stating "kubelet takes care of containers described in the pod specifications." [1] http://kubernetes.io/docs/admin/kubelet/ Other piece of info [1]: "Many of these containers run under the management of the kubelet binary, which attempts to keep containers running, even if they fail. So, in order to turn down the cluster, you need to first kill the kubelet container, and then any other containers." Stating kubelet runs kubelet containers. [1] http://kubernetes.io/docs/getting-started-guides/docker/ Information you are looking for is in the documentation but broken apart on many places. Nothing tells users why these messages are printed out and if they need to do anything to correct that. The above quotes do not indicate whether which containers are ok to be listed as such and which not. What are these having to do with OpenShift "goofy_yonath", "loving_curie"? I don't say they don't belong. It's just not clear and I as a user would be wondering what are these and is it normal to see such messages. I mean that a little more explanation in documentation is what we need in my opinion. Upstream PR here: https://github.com/kubernetes/kubernetes/pull/30435. Once merged, it can be rebased in Origin. Merged upstream. Once the openshift gets rebased, this can be closed. |