<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts on Mircea Anton</title><link>https://mirceanton.com/posts/</link><description>Recent content in Posts on Mircea Anton</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://mirceanton.com/posts/feed.xml" rel="self" type="application/rss+xml"/><item><title>RouterOS as a Whole Homelab: Router, NAS and Apps on a ZimaBoard 2</title><link>https://mirceanton.com/posts/routeros-zimaboard-2-homelab/</link><pubDate>Tue, 10 Nov 2026 00:00:00 +0000</pubDate><guid>https://mirceanton.com/posts/routeros-zimaboard-2-homelab/</guid><description>&lt;p&gt;I recently put MikroTik&amp;rsquo;s RouterOS on a ZimaBoard 2 and gave it three jobs at once: router, NAS and application server. No Proxmox, no VMs, just RouterOS running the whole thing. You can watch the &lt;a href="https://www.youtube.com/watch?v=Q6FP4Vwik5U"&gt;YouTube video&lt;/a&gt; for the full story and the test results.&lt;/p&gt;&#10;&lt;p&gt;This post is the companion to that video. It&amp;rsquo;s less narrative and more of the actual config, broken down section by section, plus a few things that didn&amp;rsquo;t make the cut. If you just want the script, you can &lt;a href="https://mirceanton.com/posts/routeros-zimaboard-2-homelab/zimarouter.rsc"&gt;download it&lt;/a&gt; as a &lt;code&gt;.rsc&lt;/code&gt; file.&lt;/p&gt;</description></item><item><title>GitOps in the Wild: How we run FluxCD at Raiffeisen Bank</title><link>https://mirceanton.com/talks/cloud-native-days-romania-2026/</link><pubDate>Mon, 18 May 2026 00:00:00 +0000</pubDate><guid>https://mirceanton.com/talks/cloud-native-days-romania-2026/</guid><description>&lt;p&gt;A few days ago I had the pleasure of attending CloudNativeDays Romania, but this year, as opposed to last year, I attended as a speaker instead of a participant. My presentation went well enough that people asked me to post the slides, which, sure, I&amp;rsquo;ll do, but a PowerPoint by itself feels a bit lonely. So here&amp;rsquo;s the companion piece: the story behind the slides, in a format that actually makes sense to read.&lt;/p&gt;</description></item><item><title>From Zero to Website in 100 Minutes</title><link>https://mirceanton.com/talks/omniopencon-2025/</link><pubDate>Fri, 17 Oct 2025 00:00:00 +0000</pubDate><guid>https://mirceanton.com/talks/omniopencon-2025/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;a class="anchor" href="#overview" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;This workshop will guide you through creating, customizing, and deploying your own website using &lt;strong&gt;Hugo&lt;/strong&gt; and &lt;strong&gt;GitHub Pages&lt;/strong&gt;, all within &lt;strong&gt;GitHub Codespaces&lt;/strong&gt;.&lt;br&gt;&#10;By the end, you will have a fully functional website hosted online, built entirely from your browser.&lt;/p&gt;&#10;&lt;h2 id="prerequisites"&gt;Prerequisites&lt;a class="anchor" href="#prerequisites" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;A &lt;strong&gt;GitHub account&lt;/strong&gt; (free)&lt;/li&gt;&#10;&lt;li&gt;No prior web development experience is required&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Everything else will be done using GitHub&amp;rsquo;s cloud tools, so you will not need to install anything locally.&lt;/p&gt;</description></item><item><title>Setting Up Ceph in My Proxmox Cluster</title><link>https://mirceanton.com/posts/setting-up-ceph-in-my-proxmox-cluster/</link><pubDate>Sat, 04 Oct 2025 00:00:00 +0000</pubDate><guid>https://mirceanton.com/posts/setting-up-ceph-in-my-proxmox-cluster/</guid><description>&lt;p&gt;If you&amp;rsquo;re following along with my homelab journey, either here or on the &lt;a href="https://www.youtube.com/@mirceanton"&gt;YouTubez&lt;/a&gt;, you might know that a few weeks ago I got a new three-node Proxmox cluster up and running.&lt;/p&gt;&#10;&lt;p&gt;It&amp;rsquo;s been great for compute, no complaints there. If a node dies, VMs can restart elsewhere. But only if they were using my NAS for storage.&lt;/p&gt;&#10;&lt;p&gt;Any VMs on local storage? Toast if that node dies. VMs on my NAS? Great until the NAS decides to take a nap. Either way, I&amp;rsquo;ve got single points of failure everywhere, and calling this &amp;ldquo;highly available&amp;rdquo; feels like I&amp;rsquo;m lying to myself.&lt;/p&gt;</description></item><item><title>Getting Started With Mikrotik and Terraform</title><link>https://mirceanton.com/posts/mikrotik-terraform-getting-started/</link><pubDate>Wed, 19 Feb 2025 00:00:00 +0000</pubDate><guid>https://mirceanton.com/posts/mikrotik-terraform-getting-started/</guid><description>&lt;p&gt;I &amp;ldquo;recently&amp;rdquo; (like&amp;hellip; almost a year ago at this point 😅) upgraded from my DIY OPNsense setup to a MikroTik RB5009. You can watch my &lt;a href="https://www.youtube.com/watch?v=k5eShv6l1ts"&gt;YouTube Video&lt;/a&gt; for the full story of the why, what and the how.&lt;/p&gt;&#10;&lt;p&gt;After much ado and months of procrastination, I&amp;rsquo;m finally getting started with my Terraform-Mikrotik network automation. This post will not be a full-blown guide or walk-through. Rather, I am just aiming to show you how to:&lt;/p&gt;</description></item><item><title>Terraform: No Backend? No Problem!</title><link>https://mirceanton.com/posts/terraform-state-git/</link><pubDate>Mon, 03 Feb 2025 00:00:00 +0000</pubDate><guid>https://mirceanton.com/posts/terraform-state-git/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;a class="anchor" href="#introduction" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;So I&amp;rsquo;ve been terraforming quite a bit lately. Since migrating from OPNsense to MikroTik, where I began automating my entire network setup, I have actually moved to a new apartment! This has pushed me to rework my &lt;strong&gt;entire&lt;/strong&gt; network configuration, and along the way, I started rethinking how I manage Terraform state.&lt;/p&gt;&#10;&lt;h2 id="traditional-state-backends"&gt;Traditional State Backends&lt;a class="anchor" href="#traditional-state-backends" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;One issue I&amp;rsquo;ve always had with &lt;code&gt;terraform&lt;/code&gt; was choosing an appropriate state backend. Granted, this could very well just be a skill issue on my side, but it was an issue nonetheless.&lt;br&gt;&#10;I must (shamefully) admit that most often I&amp;rsquo;m just using the default &lt;code&gt;local&lt;/code&gt; backend, which stores the state file in a local directory.&lt;/p&gt;</description></item><item><title>My Kubernetes Certification Journey</title><link>https://mirceanton.com/posts/kubernetes-certification-journey/</link><pubDate>Tue, 10 Dec 2024 00:00:00 +0000</pubDate><guid>https://mirceanton.com/posts/kubernetes-certification-journey/</guid><description>&lt;p&gt;Back in &amp;lsquo;22 (2022, that is), I decided to challenge myself and get all three Kubernetes certifications within 3 weeks. One week per exam. Looking back, I&amp;rsquo;m not entirely sure if this was ambitious or just plain stupid, but hey, I pulled it off! Let me walk you through my entire journey, exam by exam, and hopefully save you from some of the pain I went through.&lt;/p&gt;&#10;&lt;p&gt;As a junior DevOps engineer with about 1.5 years of experience at the time, I felt reasonably confident going into this challenge. It appears that my confidence was justified for two of the exams, but the third one&amp;hellip; well, we&amp;rsquo;ll get to that.&lt;/p&gt;</description></item><item><title>Doing Secrets The GitOps Way</title><link>https://mirceanton.com/posts/doing-secrets-the-gitops-way/</link><pubDate>Tue, 26 Mar 2024 00:00:00 +0000</pubDate><guid>https://mirceanton.com/posts/doing-secrets-the-gitops-way/</guid><description>&lt;p&gt;Alrighty then, let&amp;rsquo;s talk GitOps.&lt;/p&gt;&#10;&lt;p&gt;I think it&amp;rsquo;s pretty neat that you can push all your manifests to Git, and just like that, your cluster auto-magically syncs up seamlessly. I also think it&amp;rsquo;s a bit of a pain to push &lt;strong&gt;all&lt;/strong&gt; manifests to git, since among those manifests lurk some secrets that definitely shouldn&amp;rsquo;t be out there for the world to see.&lt;/p&gt;&#10;&lt;p&gt;In this blog post, alongside a &lt;a href="https://youtu.be/wqD7k5iNvqs"&gt;YouTube video&lt;/a&gt; I&amp;rsquo;ve put together, I&amp;rsquo;m going over one of the solutions that allows me to simply push those secret files to git without worrying about them.&lt;/p&gt;</description></item><item><title>The Best OS For Kubernetes</title><link>https://mirceanton.com/posts/the-best-os-for-kubernetes/</link><pubDate>Tue, 28 Nov 2023 00:00:00 +0000</pubDate><guid>https://mirceanton.com/posts/the-best-os-for-kubernetes/</guid><description>&lt;p&gt;If you&amp;rsquo;re not using Talos Linux for Kubernetes, you&amp;rsquo;re &lt;em&gt;probably&lt;/em&gt; doing it wrong. Read along and let me explain why.&lt;/p&gt;&#10;&lt;h2 id="the-relic-of-the-past"&gt;The Relic of the Past&lt;a class="anchor" href="#the-relic-of-the-past" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;&lt;img src="https://mirceanton.com/posts/the-best-os-for-kubernetes/img/ubuntu-old_hu_341d5345f20cbb4a.webp" alt="Old Ubuntu being old" srcset="https://mirceanton.com/posts/the-best-os-for-kubernetes/img/ubuntu-old_hu_69409061c8005283.webp 800w, https://mirceanton.com/posts/the-best-os-for-kubernetes/img/ubuntu-old_hu_341d5345f20cbb4a.webp 1600w" sizes="(max-width: 860px) 100vw, 800px" data-zoom="/posts/the-best-os-for-kubernetes/img/ubuntu-old_hu_a7519d2ed260f39b.webp" width="1600" height="692" data-lqip style="background-image:url(data:image/webp;base64,UklGRmIAAABXRUJQVlA4IFYAAAAQBACdASoYAAoAPqU8l0QjIaEYBAAzCkT0AEAABM2V33p2w16J2hTLAAD++hnIDU831rJVS9PyaMVbLaG/8HRT/8UxRIr1BMocacJGU4iq9CHsa4AAAA==)"ZgotmplZ loading="lazy" decoding="async"&gt;&#10;&lt;em&gt;&amp;ldquo;Old Ubuntu Being Old&amp;rdquo; by &lt;a href="https://bomkii.com"&gt;bomkii&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;When setting up an on-prem Kubernetes cluster, the usual process involves installing, configuring and hardening a base OS like Ubuntu or RHEL, installing a 3rd party tool to deploy kubernetes and then - &lt;em&gt;finally&lt;/em&gt; - deploying Kubernetes. While this approach is not wrong per-se, it has plenty of drawbacks.&lt;/p&gt;</description></item></channel></rss>