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

OPTIONS:

30       --authfile=path
31
32
33       Path of the authentication file. Default is ${XDG_RUNTIME_DIR}/contain‐
34       ers/auth.json, which is set using podman login.  If  the  authorization
35       state  is  not found there, $HOME/.docker/config.json is checked, which
36       is set using docker login. (Not available for remote commands)
37
38
39       Note: You can also override the default path of the authentication file
40       by  setting  the  REGISTRY_AUTH_FILE  environment variable. export REG‐
41       ISTRY_AUTH_FILE=path
42
43
44       --cert-dir=path
45
46
47       Use certificates at path (*.crt, *.cert, *.key) to connect to the  reg‐
48       istry.  Default certificates directory is /etc/containers/certs.d. (Not
49       available for remote commands)
50
51
52       --creds
53
54
55       The [username[:password]] to use to authenticate with the  registry  if
56       required.   If  one  or  both  values  are not supplied, a command line
57       prompt will appear and the value  can  be  entered.   The  password  is
58       entered without echo.
59
60
61       --quiet, -q
62
63
64       Suppress output information when pulling images
65
66
67       --tls-verify=true|false
68
69
70       Require  HTTPS  and  verify  certificates  when  contacting  registries
71       (default: true). If explicitly set to true, then TLS verification  will
72       be  used.  If  set to false, then TLS verification will not be used. If
73       not specified, TLS verification will be used unless the target registry
74       is  listed  as  an insecure registry in registries.conf. (Not available
75       for remote commands)
76
77
78       --help, -h
79
80
81       Print usage statement
82
83

Examples

85       Recreate the pod and containers as described in a file called demo.yml
86
87
88              $ podman play kube demo.yml
89              52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6
90
91
92

SEE ALSO

94       podman(1), podman-container(1), podman-pod(1), podman-generate-kube(1),
95       podman-play(1)
96
97

HISTORY

99       December 2018, Originally compiled by Brent Baude (bbaude at redhat dot
100       com)
101
102
103
104                                                         podman-play-kube(1)()
Impressum