<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>hands-on on David An</title>
    <link>https://davidan.dev/tags/hands-on/</link>
    <description>Recent content in hands-on on David An</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 01 Jun 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://davidan.dev/tags/hands-on/index.xml" rel="self" type="application/rss+xml" />
    <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>
    
  </channel>
</rss>
