<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>devops on David An</title>
    <link>https://davidan.dev/tags/devops/</link>
    <description>Recent content in devops 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/devops/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>
    
    <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>
