1podman-play-kube(1)()                                    podman-play-kube(1)()
2
3
4

NAME

6       podman-play-kube - Create pods and containers based on Kubernetes YAML
7
8

SYNOPSIS

10       podman play kube [options] file.yml
11
12

DESCRIPTION

14       podman play kube will read in a structured file of Kubernetes YAML.  It
15       will then recreate the pod and containers described in the  YAML.   The
16       containers within the pod are then started and the ID of the new Pod is
17       output.
18
19
20       Ideally the input file would be one created by Podman (see  podman-gen‐
21       erate-kube(1)).   This  would  guarantee  a  smooth import and expected
22       results.
23
24
25       Note: HostPath volume types created by  play  kube  will  be  given  an
26       SELinux private label (Z)
27
28
29       Note: If the :latest tag is used, Podman will attempt to pull the image
30       from a registry. If the image was built locally with Podman or Buildah,
31       it will have localhost as the domain, in that case, Podman will use the
32       image from the local store even if it has the :latest tag.
33
34

OPTIONS

36   --authfile=path
37       Path of the authentication file. Default is ${XDG_RUNTIME_DIR}/contain‐
38       ers/auth.json,  which  is set using podman login.  If the authorization
39       state is not found there, $HOME/.docker/config.json is  checked,  which
40       is set using docker login.
41
42
43       Note: You can also override the default path of the authentication file
44       by setting the REGISTRY_AUTH_FILE  environment  variable.  export  REG‐
45       ISTRY_AUTH_FILE=path
46
47
48   --cert-dir=path
49       Use  certificates at path (*.crt, *.cert, *.key) to connect to the reg‐
50       istry.  Default certificates directory is /etc/containers/certs.d. (Not
51       available for remote commands)
52
53
54   --configmap=path
55       Use  Kubernetes configmap YAML at path to provide a source for environ‐
56       ment variable values within the containers of the pod.
57
58
59       Note: The --configmap option can be used multiple times or a comma-sep‐
60       arated  list of paths can be used to pass multiple Kubernetes configmap
61       YAMLs.
62
63
64   --creds
65       The [username[:password]] to use to authenticate with the  registry  if
66       required.   If  one  or  both  values  are not supplied, a command line
67       prompt will appear and the value  can  be  entered.   The  password  is
68       entered without echo.
69
70
71   --log-driver=driver
72       Set logging driver for all created containers.
73
74
75   --network=networks, --net
76       A  comma-separated  list  of  the  names of CNI networks the pod should
77       join.
78
79
80   --quiet, -q
81       Suppress output information when pulling images
82
83
84   --seccomp-profile-root=path
85       Directory path for seccomp  profiles  (default:  "/var/lib/kubelet/sec‐
86       comp"). (Not available for remote commands)
87
88
89   --start=true|false
90       Start the pod after creating it, set to false to only create it.
91
92
93   --tls-verify=true|false
94       Require  HTTPS  and  verify  certificates  when  contacting  registries
95       (default: true). If explicitly set to true, then TLS verification  will
96       be  used.  If  set to false, then TLS verification will not be used. If
97       not specified, TLS verification will be used unless the target registry
98       is listed as an insecure registry in registries.conf.
99
100
101   --help, -h
102       Print usage statement
103
104

EXAMPLES

106       Recreate the pod and containers as described in a file called demo.yml
107
108
109              $ podman play kube demo.yml
110              52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6
111
112
113
114       Provide configmap-foo.yml and configmap-bar.yml as sources for environ‐
115       ment variables within the containers.
116
117
118              $ podman play kube demo.yml --configmap configmap-foo.yml,configmap-bar.yml
119              52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6
120
121              $ podman play kube demo.yml --configmap configmap-foo.yml --configmap configmap-bar.yml
122              52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6
123
124
125
126       CNI network(s) can be specified as comma-separated list using --network
127
128
129              $ podman play kube demo.yml --network cni1,cni2
130              52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6
131
132
133
134       Please take into account that CNI networks must be created first  using
135       podman-network-create(1).
136
137

SEE ALSO

139       podman(1), podman-container(1), podman-pod(1), podman-generate-kube(1),
140       podman-play(1), podman-network-create(1)
141
142

HISTORY

144       December 2018, Originally compiled by Brent Baude (bbaude at redhat dot
145       com)
146
147
148
149                                                         podman-play-kube(1)()
Impressum