Score:0

how to determine kubernetes pod's runtime command definitively

za flag
Jim

For purposes beyond that which is necessary to describe here, it is necessary for me, in order to accomplish my goal, to exec into pods, determine the primary process's PID, and then perform some actions in running pods' /proc/<PID>/.

So the problem is obvious perhaps. Given arbitrary pods, how can one programmatically determine the main PID (not side-cars) in running pods realizing that the ENTRYPOINT in the container image is the COMMAND to kubernetes and that specific overrides can occur if COMMAND is specified (thus one could simply describe or get -o yaml the pod, but that is not scalable because not all pods are run/created equal. So such queries would only be right sometimes)...

Is there definitive way to accomplish this goal and if so, what is it? I don't think there's a really solid way to do this, but I want to confirm that.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.