Podman and Kubernetes are a common pairing in a modern DevOps stack. Here is how they fit together and a practical way to wire them up.
Where Podman fits
Podman runs OCI containers without a central daemon and supports rootless containers by default, with a Docker-compatible CLI and the ability to generate Kubernetes YAML from pods.
podman run -d --name web -p 8080:80 nginx:alpine
podman generate systemd --new --name web > ~/.config/systemd/user/web.service
systemctl --user enable --now webWhere Kubernetes fits
Kubernetes is a container orchestrator: you declare the desired state of your workloads in YAML and controllers continuously reconcile the cluster toward it, handling scheduling, scaling, healing and networking.
apiVersion: apps/v1
kind: Deployment
metadata: { name: web }
spec:
replicas: 3
selector: { matchLabels: { app: web } }
template:
metadata: { labels: { app: web } }
spec:
containers:
- name: web
image: ghcr.io/acme/web:1.0
ports: [{ containerPort: 3000 }]
resources:
requests: { cpu: 100m, memory: 128Mi }
limits: { cpu: 500m, memory: 256Mi }
readinessProbe:
httpGet: { path: /healthz, port: 3000 }
---
apiVersion: v1
kind: Service
metadata: { name: web }
spec:
selector: { app: web }
ports: [{ port: 80, targetPort: 3000 }]Making them work together
- Prefer rootless containers and Quadlet/systemd for services
- Use podman generate kube to bridge to Kubernetes
- Set requests/limits and use the HorizontalPodAutoscaler for elastic workloads
- Separate config (ConfigMap) from secrets and mount them, don't bake them in
Want this pairing set up properly, with docs and handover? That is exactly the kind of work CodeWizard's embedded senior engineers do - and both Podman and Kubernetes have active community groups you can join for free.