summaryrefslogtreecommitdiff
path: root/cmd/podman/sigproxy.go
diff options
context:
space:
mode:
authorbaude <bbaude@redhat.com>2019-02-26 11:13:23 -0600
committerbaude <bbaude@redhat.com>2019-02-26 12:13:12 -0600
commited1ea8dea1b2738829a05dd3c3dbcf4b6744ad3f (patch)
tree7a7f4466c4909fe2b5121badfb6e3cfc2e9e03d8 /cmd/podman/sigproxy.go
parent1ad0d29fc2eb52fec707a4458fe31adc862e2862 (diff)
downloadpodman-ed1ea8dea1b2738829a05dd3c3dbcf4b6744ad3f.tar.gz
podman-ed1ea8dea1b2738829a05dd3c3dbcf4b6744ad3f.tar.bz2
podman-ed1ea8dea1b2738829a05dd3c3dbcf4b6744ad3f.zip
rename pod when we have a name collision with a container
when podman generate kube runs, it names the pod based on the first container it finds. the resulting yaml file is perfectly acceptable in a kubernetes environment. But when replaying the YAML file with podman, we cannot have a container and pod with the same name. therefore, we rename the pod if find a collision to name_pod. Signed-off-by: baude <bbaude@redhat.com>
Diffstat (limited to 'cmd/podman/sigproxy.go')
0 files changed, 0 insertions, 0 deletions