<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Netbox on DevOps von UCLAB</title>
    <link>https://uclab.dev/tags/netbox/</link>
    <description>Recent content in Netbox on DevOps von UCLAB</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 28 Mar 2026 07:41:10 +0000</lastBuildDate>
    <atom:link href="https://uclab.dev/tags/netbox/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Deploying NetBox on k3s</title>
      <link>https://uclab.dev/posts/netbox/</link>
      <pubDate>Sat, 28 Mar 2026 07:41:10 +0000</pubDate>
      <guid>https://uclab.dev/posts/netbox/</guid>
      <description>&lt;p&gt;NetBox is the source of truth for network and infrastructure documentation. If you run a homelab or a small datacenter and want to know what IP belongs where, what VLANs exist, and which rack holds which server — NetBox is the tool for the job. This post walks through deploying it on a k3s cluster using the official Helm chart, FluxCD for GitOps, and HashiCorp Vault via ExternalSecrets for secret management.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
