<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Nas on DevOps von UCLAB</title>
    <link>https://uclab.dev/tags/nas/</link>
    <description>Recent content in Nas on DevOps von UCLAB</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 04 Apr 2026 11:24:04 +0000</lastBuildDate>
    <atom:link href="https://uclab.dev/tags/nas/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Vault on a Synology NAS and Migrating Secrets</title>
      <link>https://uclab.dev/posts/vault-migrate/</link>
      <pubDate>Sat, 04 Apr 2026 11:24:04 +0000</pubDate>
      <guid>https://uclab.dev/posts/vault-migrate/</guid>
      <description>&lt;p&gt;I recently needed to migrate my HashiCorp Vault instance from a dedicated Ubuntu VM to a Docker container running on my Synology DS918+ NAS. This post covers the entire process: setting up Vault on Synology, configuring it behind the built-in reverse proxy, creating a proper policy and user structure, and finally migrating all secrets from the old instance — including re-connecting everything to an External Secrets Operator running in a k3s cluster.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
