Documentation Index
Fetch the complete documentation index at: https://mintlify.com/Pratyay360/podman-ts/llms.txt
Use this file to discover all available pages before exploring further.
KubeManager bridges Podman and Kubernetes by letting you generate Kubernetes YAML from running containers and pods, apply YAML workloads back into Podman, and produce systemd unit files for any named resource. It is accessible via client.kube on any PodmanClient instance.
KubeManager does not extend Manager and has no list() or get() method — it is a stateless operation surface, not a resource manager.KubeManager methods
generate
apply() or play().
One or more container or pod names/IDs to include in the generated YAML.
Include the pod(s) that own the named containers in the output.
Set the replica count when the generated resource type is
Deployment.Append a Kubernetes
Service object alongside the workload resource.Kubernetes resource type to generate (e.g.
"Deployment", "Job"). Defaults to the Podman API’s built-in choice.Do not truncate container/pod IDs in the generated output.
generateSystemd
{ "container-myapp.service": "..." }).
Container or pod name/ID.
Use the container/pod name rather than its ID in the generated unit name.
Generate a unit that creates a new container on start instead of restarting an existing one.
Omit the comment header from the generated unit file.
TimeoutStartSec value in seconds.TimeoutStopSec value in seconds.Systemd
Restart directive (e.g. "on-failure", "always", "no").Prefix for container unit names. Defaults to
"container".Prefix for pod unit names. Defaults to
"pod".Separator between the prefix and the container/pod name (e.g.
"-" or "_").Additional
Wants= dependencies to add to the [Unit] section.Additional
After= ordering dependencies.Additional
Requires= hard dependencies.Extra
Environment= lines to inject (e.g. ["MY_VAR=value"]).apply
YAML content as a string.
Path to a CA certificate file used for TLS verification against the target cluster.
Path to a kubeconfig file. When set, the YAML is applied to the configured Kubernetes cluster instead of the local Podman service.
Kubernetes namespace to apply the resources into.
Path at which to save the YAML file on the server before applying.
Service account name to use when applying the resources.
play
podman play kube). Returns a summary of created resources.
YAML content as a string.
Annotations to attach to created pods.
Path to a registry auth file for pulling images.
Network mode or network names to attach pods to.
Tear down and recreate pods that already exist.
Start pods immediately after creation (default behaviour when omitted).
Verify TLS certificates when pulling images.
Paths to ConfigMap YAML files to make available during play.
Build images from Containerfiles referenced in the YAML before running.
Suppress image pull progress output.
Log driver for created containers (e.g.
"journald", "k8s-file").playDown
play() call. Pass the same YAML that was used for play(). Returns a summary of removed resources.
The same YAML string that was passed to
play().Force removal even if containers are still running.