podman-kube-down(1)

📦
version 6.1.4 · 6 versions
, in arch rolling

💅 podman-kube-down — the manual page, but make it cute

Ok so bestie, welcome to podman-kube-down — the part of the podman kube</> family that ✨cleans up✨ after you. It lives in the General Commands Manual, and honestly? It's giving "the friend who helps you pack up after the party" energy. 🎀

🌸 NAME 🌸

podman-kube-down — remove containers and pods based on Kubernetes YAML. That's it, that's the whole job. 🧹

✨ SYNOPSIS ✨

podman kube down [options] file.yml|-|https://website.io/file.yml
[file2.yml|https://website.io/file2.yml ...]

Yup, you can feed it a local file, a literal - for stdin, or a whole URL, and you can stack as many as you want in one go. Main character multitasking. 👑

🦋 DESCRIPTION 🦋

So here's the vibe: podman kube down reads one or more Kubernetes YAML files you point it at, and it tears down the pods that were created by the podman kube play command using those same Kubernetes YAML files. Matching set, no cap. 💖

Any volumes that were created by the previous podman kube play command remain intact — like, they survive — unless you use the --force option. So if you were hoping your volumes would also vanish, ngl, you gotta be explicit about it.

If the YAML file is specified as -, then podman kube down reads the YAML from stdin. Classic. 🫶

Your inputs can also be URLs that point to YAML files, like https://podman.io/demo.yml. podman kube down tears down the pods and containers created by podman kube play via the same Kubernetes YAML from the URLs. However — and this is the important part, bestie, underline it twice — podman kube down does not work with a URL if the YAML file the URL points to has been changed or altered since the creation of the pods and containers using podman kube play. It's gotta be the same YAML. Periodt. 🔥

When multiple YAML files are specified (local files, URLs, or a combination), they are processed sequentially and combined with YAML document separators (---), just like with podman kube play. Iconic consistency. 🌈

💅 OPTIONS 💅

  • --force — Remove all resources, including volumes, when calling podman kube down. Yes, all of them. The volumes too. Go off. 💀

🎀 EXAMPLES 🎀

⭐ Example YAML file demo.yml

apiVersion: v1
kind: Pod
metadata:
...
spec:
  containers:
  - command:
    - top
    - name: container
      value: podman
    image: foobar
...

🧚 Remove the pod and containers as described in the demo.yml file

$ podman kube down demo.yml
Pods stopped:
52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6
Pods removed:
52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6

🍓 Remove the pod and containers as described in the demo.yml file, YAML sent to stdin

$ cat demo.yml | podman kube play -
Pods stopped:
52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6
Pods removed:
52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6

(Pipe it in, let stdin do its thing. Slay. 🫶)

🔥 Remove the pods and containers as described in the demo.yml file, YAML read from a URL

$ podman kube down https://podman.io/demo.yml
Pods stopped:
52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6
Pods removed:
52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6
⚠️ ok so real talk: podman kube down does not work with a URL if the YAML file the URL points to has been changed or altered since it was used to create the pods and containers. Changed YAML = no match = no teardown. 😭

🌈 Remove the pods and containers that were created from multiple YAML files

$ podman kube down pod.yml service.yml configmap.yml
Pods stopped:
52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6
Pods removed:
52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6

👑 Remove the pods and containers that were created from multiple URLs

$ podman kube down https://example.com/pod.yml https://example.com/service.yml https://example.com/configmap.yml
Pods stopped:
52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6
Pods removed:
52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6

💜 Remove the pods and containers that were created from a combination of local files and URLs

$ podman kube down local-pod.yml https://example.com/service.yml local-configmap.yml
Pods stopped:
52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6
Pods removed:
52182811df2b1e73f36476003a66ec872101ea59034ac0d4d3a7b40903b955a6

Local files and URLs in the same command? Mixing it up, we love to see it. 🌸

💖 SEE ALSO 💖

podman(1), podman-kube(1), podman-kube-play(1), podman-kube-generate(1), containers-certs.d(5)

Go read those too, bestie, they're literally the whole ecosystem. iykyk. 🦋

ok bye ily, go tear down some pods responsibly 💅✨ — this cutie patootie page is podman-kube-down(1) from the General Commands Manual, and you're reading the podman-kube-down(1) footer, so yeah, that's the whole thing. mwah. 🎀

📦 where this page comes from