<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>kubernetes on Alekc's Blog</title><link>https://blog.alekc.org/tags/kubernetes/</link><description>Recent content in kubernetes on Alekc's Blog</description><generator>Hugo -- gohugo.io</generator><copyright>©{year}, All Rights Reserved</copyright><lastBuildDate>Sat, 03 Dec 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.alekc.org/tags/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>Useful debugging tools for kubernetes</title><link>https://blog.alekc.org/posts/useful-debugging-tools-for-kubernetes/</link><pubDate>Sat, 03 Dec 2022 00:00:00 +0000</pubDate><guid>https://blog.alekc.org/posts/useful-debugging-tools-for-kubernetes/</guid><description>Sometimes its useful to be able to run some ephemeral containers on kubernetes cluster in order to perform some debugging (i.e. dns resolution, pinging nodes, etc).
Sadly, most of the times, it can be tricky to remember all overrides so here is a small list
Run an ephemeral shell on a random node 1kubectl run -ti --restart=Never --rm debug --image=alekcander/network-diag -- sh Run a container with specific service account 1kubectl run -ti --restart=Never --rm debug --image=alekcander/network-diag --overrides=&amp;#39;{ &amp;#34;spec&amp;#34;: { &amp;#34;serviceAccount&amp;#34;: &amp;#34;terraform-runner&amp;#34; } }&amp;#39; -- sh Run on a specific node 1kubectl run -ti --restart=Never --rm debug --image=alekcander/network-diag --overrides=&amp;#39;{&amp;#34;spec&amp;#34;: { &amp;#34;nodeName&amp;#34;: &amp;#34;alekc-worker-01&amp;#34;}}&amp;#39; -- sh Run based on specific selector (ie.</description></item><item><title>How to create terraform iam roles for irsa functionality</title><link>https://blog.alekc.org/posts/how-to-create-terraform-iam-roles-for-irsa-functionality/</link><pubDate>Tue, 18 Jan 2022 16:00:00 +0000</pubDate><guid>https://blog.alekc.org/posts/how-to-create-terraform-iam-roles-for-irsa-functionality/</guid><description>&lt;p>IRSA (IAM role for service account) is a very useful tool which permits us to provide AWS permissions to the containers in any pod that uses that service account. This enables us to give a very granular permission setting for specific service accounts and remove most of the headache related to authentication and persisting of secrets.&lt;/p>
&lt;p>Below a quick snippet of how to create such mechanism.&lt;/p></description></item><item><title>Use terraform http data source to wait for cluster coming up</title><link>https://blog.alekc.org/posts/use-terraform-http-data-source-for-cluster-health-check/</link><pubDate>Tue, 18 Jan 2022 00:00:00 +0000</pubDate><guid>https://blog.alekc.org/posts/use-terraform-http-data-source-for-cluster-health-check/</guid><description>&lt;p>Neat example of how we can use terraform http data source to wait for our kubernetes cluster to come up with a healthy state (shamelessly taken from some github repo)&lt;/p></description></item></channel></rss>