diff options
| author | Urvashi Mohnani <umohnani@redhat.com> | 2021-08-25 12:37:51 -0400 |
|---|---|---|
| committer | Urvashi Mohnani <umohnani@redhat.com> | 2021-09-10 09:37:46 -0400 |
| commit | f5e4ffb5e46be03a81b4425d3fe080543fca7035 (patch) | |
| tree | 979f0e8aee5aebaa8b41cf0620d311381e6a9f20 /pkg/domain/entities | |
| parent | 580ac4c6abc336d984f3a09940a4ef3006f0e6a7 (diff) | |
| download | podman-f5e4ffb5e46be03a81b4425d3fe080543fca7035.tar.gz podman-f5e4ffb5e46be03a81b4425d3fe080543fca7035.tar.bz2 podman-f5e4ffb5e46be03a81b4425d3fe080543fca7035.zip | |
Add init containers to generate and play kube
Kubernetes has a concept of init containers that run and exit before
the regular containers in a pod are started. We added init containers
to podman pods as well. This patch adds support for generating init
containers in the kube yaml when a pod we are converting had init
containers. When playing a kube yaml, it detects an init container
and creates such a container in podman accordingly.
Note, only init containers created with the init type set to "always"
will be generated as the "once" option deletes the init container after
it has run and exited. Play kube will always creates init containers
with the "always" init container type.
Signed-off-by: Urvashi Mohnani <umohnani@redhat.com>
Diffstat (limited to 'pkg/domain/entities')
| -rw-r--r-- | pkg/domain/entities/play.go | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/pkg/domain/entities/play.go b/pkg/domain/entities/play.go index 77329e328..f630b3f24 100644 --- a/pkg/domain/entities/play.go +++ b/pkg/domain/entities/play.go @@ -51,6 +51,8 @@ type PlayKubePod struct { ID string // Containers - the IDs of the containers running in the created pod. Containers []string + // InitContainers - the IDs of the init containers to be run in the created pod. + InitContainers []string // Logs - non-fatal errors and log messages while processing. Logs []string // ContainerErrors - any errors that occurred while starting containers |