<?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 David An</title>
    <link>https://davidan.dev/tags/kubernetes/</link>
    <description>Recent content in kubernetes on David An</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 14 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://davidan.dev/tags/kubernetes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Local-first GPU Cluster with nvkind and Time Splitting</title>
      <link>https://davidan.dev/posts/nvkind/</link>
      <pubDate>Sun, 14 Dec 2025 00:00:00 +0000</pubDate>
      
      <guid>https://davidan.dev/posts/nvkind/</guid>
      <description>You have a brand new shiny GPU and want to start experimenting with it by running some sample experiments in Kubernetes, but how would you start that. In this short tutorial, we go over how to use nvkind, the gpu-operator to start running some basic experiemtns using your new GPU. We assume that the reader already has things such as Docker, golang, and relevant drivers/systems (nvidia-ctk, nvidia-smi, etc.) installed too.</description>
    </item>
    
    <item>
      <title>Distributed Inference for Fun and Profit</title>
      <link>https://davidan.dev/posts/dif/</link>
      <pubDate>Sat, 01 Nov 2025 00:00:00 +0000</pubDate>
      
      <guid>https://davidan.dev/posts/dif/</guid>
      <description>You ever just wonder how large models serve at scale? Or how to actually go from query to answer? Over the course of this article, we will take a look at approaches to inference and explore the tradeoffs of various approaches from a technical perspective.
We assume that the reader has basic knowledge of ML concepts and how Transformers work. Additionally, all of the work here is done on a single Nvidia RTX 3090 GPU with the respective drivers installed (nvidia-smi, nvidia-ctk, etc.</description>
    </item>
    
    <item>
      <title>Implementing Kubernetes Security: A Hands-On Approach</title>
      <link>https://davidan.dev/posts/k8s-2/</link>
      <pubDate>Sun, 01 Jun 2025 00:00:00 +0000</pubDate>
      
      <guid>https://davidan.dev/posts/k8s-2/</guid>
      <description>In a continuation of the previous article, we explore the implementation of these different examples. Specifically, we will be covering workload separation, authentication, and other hardedning techniques. This article will have an example followed by a short explanation of what and why we should do that. We assume that the reader has a basic understanding of Kubernetes topics such as pods, service accounts, and secrets.
Read Only File-Systems Read Only File System with Mounted Volume Show All Show Less spec: containers: - command: [&#34;</description>
    </item>
    
    <item>
      <title>An Intro to Kubernetes Security</title>
      <link>https://davidan.dev/posts/k8s/</link>
      <pubDate>Sat, 06 Jul 2024 00:00:00 +0000</pubDate>
      
      <guid>https://davidan.dev/posts/k8s/</guid>
      <description>Kubernetes is now widely used for managing containerized applications. As more organizations adopt it, understanding its security aspects becomes crucial. This paper examines the key security challenges in Kubernetes and suggests ways to address them.
Basic Concepts of Kubernetes Security Kubernetes operates across many computers, often in different locations. This spread-out nature makes security more complex. Kubernetes also constantly creates and removes small units of work called pods. This constant change means that old security methods designed for unchanging systems don&amp;rsquo;t work well.</description>
    </item>
    
  </channel>
</rss>
