<?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 Maxwell Lanzkron-Tamarazo</title>
    <link>https://www.maxwell-lt.dev/posts/</link>
    <description>Recent content in Posts on Maxwell Lanzkron-Tamarazo</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2025 Maxwell Lanzkron-Tamarazo</copyright>
    <lastBuildDate>Sun, 05 Jan 2025 21:30:00 -0500</lastBuildDate><atom:link href="https://www.maxwell-lt.dev/posts/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Tekton on K3s</title>
      <link>https://www.maxwell-lt.dev/posts/tekton-on-k3s/</link>
      <pubDate>Sun, 05 Jan 2025 21:30:00 -0500</pubDate>
      
      <guid>https://www.maxwell-lt.dev/posts/tekton-on-k3s/</guid>
      <description>&lt;p&gt;I&amp;rsquo;m currently working on a game development project, and I need a way to automatically build and deploy it. As the &lt;a href=&#34;https://tekton.dev/&#34; target=&#34;_blank&#34;&gt;Tekton&lt;/a&gt; expert and pipeline guru on my team at Ford Motor Company, I figured I&amp;rsquo;d set up a Tekton CI/CD pipeline for the game on my own hardware.&lt;/p&gt;
&lt;p&gt;Since it runs on Kubernetes, getting Tekton running on bare metal is a bit of a challenge. I previously set up a &lt;a href=&#34;https://k3s.io/&#34; target=&#34;_blank&#34;&gt;K3s&lt;/a&gt; cluster and configured &lt;a href=&#34;https://argo-cd.readthedocs.io/en/stable/&#34; target=&#34;_blank&#34;&gt;ArgoCD&lt;/a&gt; to declaratively manage it, so this post will walk through the process of assembling a Tekton pipeline on that stack.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
