<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubernetes &amp; Containers on Tuna Cinsoy</title><link>https://tunacinsoy.com/areas/kubernetes/</link><description>Recent content in Kubernetes &amp; Containers on Tuna Cinsoy</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><lastBuildDate>Fri, 27 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://tunacinsoy.com/areas/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes</title><link>https://tunacinsoy.com/posts/kubernetes/</link><pubDate>Fri, 27 Feb 2026 00:00:00 +0000</pubDate><guid>https://tunacinsoy.com/posts/kubernetes/</guid><description>&lt;p&gt;&lt;strong&gt;Q) How does the &amp;lsquo;inside of node&amp;rsquo; networking work on AKS?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;It depends on which network plugin that the cluster uses: &lt;strong&gt;Azure CNI&lt;/strong&gt;, or &lt;strong&gt;kubenet&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;In &lt;strong&gt;Azure CNI&lt;/strong&gt; setting, pods are treated as if they are individual compute resources on Azure, meaning that they will get a private IP address from the subnet that the AKS is in.&lt;/p&gt;
&lt;p&gt;In &lt;strong&gt;Kubenet&lt;/strong&gt;, the node itself does SNAT for outgoing connections - the pods within the node gets their own private ip address, completely isolated from hub-and-spoke architecture.&lt;/p&gt;</description></item><item><title>Istio</title><link>https://tunacinsoy.com/posts/istio/</link><pubDate>Mon, 05 Jan 2026 00:00:00 +0000</pubDate><guid>https://tunacinsoy.com/posts/istio/</guid><description>&lt;p&gt;&lt;strong&gt;Q) Why do we need to use Istio?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Kubernetes effectively addresses some management issues, it primarily serves as a container orchestration platform and excels in that role. However, it doesn’t inherently solve all the complexities of a microservices architecture as they require specific solutions. Kubernetes does not inherently provide robust service management capabilities.&lt;/p&gt;
&lt;p&gt;Istio steps in by injecting a sidecar container into your pod, which acts as a proxy. Your containers communicate with other containers via this proxy. This architecture allows all requests to flow through the proxy, enabling you to exert control over the traffic and collect data for further analysis. Moreover, Istio provides the means to encrypt communication between pods and enforce identity and access management through a unified control plane.&lt;/p&gt;</description></item><item><title>Kiali</title><link>https://tunacinsoy.com/posts/kiali/</link><pubDate>Fri, 02 Jan 2026 00:00:00 +0000</pubDate><guid>https://tunacinsoy.com/posts/kiali/</guid><description>&lt;p&gt;&lt;strong&gt;Q) What is Kiali?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Kiali is a powerful observability and visualization tool for microservices and service mesh management. It offers real-time insights into the behavior of your service mesh, helping you monitor and troubleshoot issues efficiently.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://tunacinsoy.com/posts/kiali/kiali-service-connectivity.png" alt=""&gt;&lt;/p&gt;</description></item><item><title>Sealed Secrets</title><link>https://tunacinsoy.com/posts/sealed-secrets/</link><pubDate>Fri, 02 Jan 2026 00:00:00 +0000</pubDate><guid>https://tunacinsoy.com/posts/sealed-secrets/</guid><description>&lt;p&gt;&lt;strong&gt;Q) What&amp;rsquo;s the benefit of using Sealed Secrets?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Sealed Secrets solves the problem of I can manage all my Kubernetes config in Git, except
Secrets. Sealed Secrets function as secure containers for your sensitive information. When you require a storage solution for secrets, such as passwords or keys, you place them in these specialized packages.&lt;/p&gt;
&lt;p&gt;Only the Sealed Secrets controller within Kubernetes can unlock and access the contents. This ensures the utmost security and protection for your valuable secrets. Created by Bitnami Labs and open sourced, they help you encrypt your Kubernetes Secrets into Sealed Secrets using asymmetric cryptography that only the Sealed Secrets controller running on the cluster can decrypt. This means you can store the Sealed Secrets in Git and use GitOps to set up everything, including Secrets.&lt;/p&gt;</description></item><item><title>Virtualization &amp; Containerization</title><link>https://tunacinsoy.com/posts/virtualization-containerization/</link><pubDate>Fri, 02 Jan 2026 00:00:00 +0000</pubDate><guid>https://tunacinsoy.com/posts/virtualization-containerization/</guid><description>&lt;p&gt;&lt;strong&gt;Q) How does the architecture of virtualization look like?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The architecture of virtualization can be seen down below.
&lt;img src="https://tunacinsoy.com/posts/virtualization-containerization/virtualization.png" alt=""&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Q) How does the architecture of containerization look like?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;The architecture of containerization can be seen down below.
&lt;img src="https://tunacinsoy.com/posts/virtualization-containerization/containerization.png" alt=""&gt;&lt;/p&gt;</description></item><item><title>Binary Authorization</title><link>https://tunacinsoy.com/posts/binary-authorization/</link><pubDate>Sun, 09 Nov 2025 00:00:00 +0000</pubDate><guid>https://tunacinsoy.com/posts/binary-authorization/</guid><description>&lt;p&gt;&lt;strong&gt;Q) What is Binary Authorization?&lt;/strong&gt;
Binary authorization is a deploy-time security mechanism that ensures that only trusted binary files are deployed within your environments. In the context of containers and Kubernetes, binary authorization uses signature validation and ensures that only container images signed by a trusted authority are deployed within Kubernetes cluster.
&lt;img src="https://tunacinsoy.com/posts/binary-authorization/bin-authz-arch.png" alt=""&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Q) How does a typical workflow look like, for deployments that utilize Binary Authorization?&lt;/strong&gt;
&lt;img src="https://tunacinsoy.com/posts/binary-authorization/k8s-binauthz-workflow.png" alt=""&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Q) Which RBAC roles should service account have?&lt;/strong&gt;
For a fully-fledged deployment, the service account / service principal should have:&lt;/p&gt;</description></item><item><title>Containerd</title><link>https://tunacinsoy.com/posts/containerd/</link><pubDate>Sun, 09 Nov 2025 00:00:00 +0000</pubDate><guid>https://tunacinsoy.com/posts/containerd/</guid><description>&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Removes images that are not currently being used by any running or stopped containers&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;crictl rmi --prune
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;</description></item><item><title>Docker</title><link>https://tunacinsoy.com/posts/docker/</link><pubDate>Sun, 09 Nov 2025 00:00:00 +0000</pubDate><guid>https://tunacinsoy.com/posts/docker/</guid><description>&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# run a docker container in detached (does not keep terminal busy while running) mode, always restart automatically when it is not stopped manually, forward host port 80 to container&amp;#39;s port 80, set memory usage limit to 1000M, allocate minimum of 250M (but it can ask for less memory, and that&amp;#39;s ok, however the upper limit is 1000M), from image &amp;#39;nginx:1.18.0&amp;#39;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;docker run -d --name &amp;lt;container_name nginx&amp;gt; --restart unless-stopped -p 80:80 &lt;span class="se"&gt;\
&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="se"&gt;&lt;/span&gt;--memory 1000M --memory-reservation 250M &amp;lt;container_image nginx:1.18.0&amp;gt;&lt;span class="sb"&gt;`&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;hr&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# For debugging purposes, create docker container using busybox image (bare minimum OS, and plus contains curl) interactively (go inside of the container after the creation completes), and after we exit from the shell, completely remove the container.&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;docker run -it --rm --name busybox-test yauritux/busybox-curl:latest
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;hr&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# list all containers&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;docker ps -a
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;hr&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Check log trace of container&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;docker logs &amp;lt;container_name OR container_id&amp;gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;hr&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Stop a container&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;docker stop &amp;lt;container_name OR container_id&amp;gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;hr&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# start a container&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;docker start &amp;lt;container_name OR container_id&amp;gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;hr&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# remove a container&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;docker rm &amp;lt;container_name OR container_id&amp;gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;hr&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# remove a container without the necessity of stopping it&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;docker rm -f &amp;lt;container_name OR container_id&amp;gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;hr&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Watch the status of containers in sync, keeps terminal busy&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;watch docker ps -a
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Q) Where do the logs of containers go?&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>External Secrets</title><link>https://tunacinsoy.com/posts/external-secrets/</link><pubDate>Sun, 09 Nov 2025 00:00:00 +0000</pubDate><guid>https://tunacinsoy.com/posts/external-secrets/</guid><description>&lt;p&gt;&lt;strong&gt;Q) What is External Secrets Operator?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;External Secrets Operator serves as a bridge between the Kubernetes cluster and external secret management systems. We define an ExternalSecret custom resource within the Kubernetes cluster, which the operator monitors. When an ExternalSecret resource is created or updated, the operator interacts with the external secret store specified in the ClusterSecretStore CRD to retrieve the secret data. It then creates or updates the corresponding Kubernetes Secrets.
&lt;img src="https://tunacinsoy.com/posts/external-secrets/ext-secrets.png" alt=""&gt;&lt;/p&gt;</description></item></channel></rss>