<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>plugin on Why did IT fail</title><link>https://www.why-did-it.fail/tags/plugin/</link><description>Recent content in plugin on Why did IT fail</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © 2026 Dominik Textoris (formerly Zorgnotti). All Rights Reserved.</copyright><lastBuildDate>Mon, 23 Dec 2019 00:00:00 +0000</lastBuildDate><atom:link href="https://www.why-did-it.fail/tags/plugin/index.xml" rel="self" type="application/rss+xml"/><item><title>A small fling - kubectl-lsdeploy</title><link>https://www.why-did-it.fail/blog/2019-08-kubectl-lsdeploy/</link><pubDate>Mon, 23 Dec 2019 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2019-08-kubectl-lsdeploy/</guid><description>I started looking a bit into Kubernetes and for no other reason than curiosity I wanted to visualize some dependencies to get a better understanding on how things work, e.g. where my container (pods) actually spawn when I apply one of these nice YAML files with a deployment. Unfortunately I wasn’t able to find a get command within kubectl that showed my all the information in a single call, except if you heavily use labels and selectors.</description></item></channel></rss>