1podman-play-kube Podman Man Pagesp(oBdrmeannt-pBlaauyd-ek)ube Podman Man Pages(Brent Baude)
2
3
4

NAME

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

SYNOPSIS

11       podman play kube [-h|--help] [--authfile] [--cert-dir] [--creds] [*-q |
12       --quiet] [--tls-verify] kubernetes_input.yml
13
14
15

DESCRIPTION

17       podman play kube will read in a structured file of Kubernetes YAML.  It
18       will then recreate the pod and containers described in the YAML.  The
19       containers within the pod are then started and the ID of the new Pod is
20       output.
21
22
23       Ideally the input file would be one created by Podman (see
24       podman-generate-kube(1)).  This would guarantee a smooth import and
25       expected results.
26
27
28       Note: HostPath volume types created by play kube will be given an
29       SELinux private label (Z)
30
31
32

OPTIONS:

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

Examples

90       Recreate the pod and containers as described in a file called demo.yml
91
92
93              $ podman play kube demo.yml
94              52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6
95
96
97

SEE ALSO

99       podman(1), podman-container(1), podman-pod(1), podman-generate-kube(1),
100       podman-play(1)
101
102
103

HISTORY

105       Decemeber 2018, Originally compiled by Brent Baude (bbaude at redhat
106       dot com)
107
108
109
110                                pDoedcmeamnb-eprla2y0-1k8ube Podman Man Pages(Brent Baude)
Impressum