Replies: 1 comment
-
Easiest way would be to add a label - io.podman.kube.source=<path> or
similar
…On Thu, Mar 25, 2021 at 10:06 Dzintars Klavins ***@***.***> wrote:
Today came across case where i have many pod-*.yml files and the running
pod. And i have no idea by which yaml file that Pod was launched. As i
see those pod files i'm sure play kube was used.
So... i would like to see some kind origin config path in the podman pod
inspect * metadata.
Sure it's not the case for CI/CD pipelines, but for some manual
development things it could be helpful.
I ended up with diffing generated pod with the existing ones.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#9815>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3AOCFKVQ3C2FS7DSJNUTTTFM7PBANCNFSM4ZZNSYFQ>
.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Today came across case where i have many
pod-*.yml
files and the running pod. And i have no idea by whichyaml
file that Pod was launched. As i see those pod files i'm sureplay kube
was used.So... i would like to see some kind
origin config path
in thepodman pod inspect *
metadata.Sure it's not the case for CI/CD pipelines, but for some manual development things it could be helpful.
I ended up with diffing generated pod with the existing ones.
Beta Was this translation helpful? Give feedback.
All reactions