<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kluctl Blog on kluctl.io</title><link>https://kluctl.io/blog/</link><description>Recent content in Kluctl Blog on kluctl.io</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="https://kluctl.io/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>ArgoCD/Flux vs Kluctl</title><link>https://kluctl.io/blog/2024/07/31/argocd-and-flux-vs-kluctl/</link><pubDate>Wed, 31 Jul 2024 00:00:00 +0000</pubDate><guid>https://kluctl.io/blog/2024/07/31/argocd-and-flux-vs-kluctl/</guid><description>Kluctl is very flexible when it comes to deployment strategies. All features implemented by Kluctl can be used via the CLI or via the Kluctl Controller.
This makes Kluctl comparable to ArgoCD and Flux, as these projects also implement the GitOps strategy.
This comparison assumes that you already know Flux and/or ArgoCD to some degree, or at least have heard of them, so it will not go too deep into comparing these against each other.</description></item><item><title>Managing Cluster API with Kluctl</title><link>https://kluctl.io/blog/2024/03/13/cluster-api-kluctl/</link><pubDate>Wed, 13 Mar 2024 00:00:00 +0000</pubDate><guid>https://kluctl.io/blog/2024/03/13/cluster-api-kluctl/</guid><description>Kubernetes started as a very promising container orchestrator and in my opinion it was very clear at day one that it would establish itself and take the market. What was not so obvious to me, was that Kubernetes would also morph into some kind of &amp;ldquo;API Platform&amp;rdquo;.
With the introduction of Custom Resource Definitions, all kinds of resources could now be managed by Kubernetes. Controllers and Operators take these Custom Resources and use the reconcile pattern to constantly reconcile the desired state with the real world.</description></item><item><title>Introducing the Kluctl Webui</title><link>https://kluctl.io/blog/2023/09/12/introducing-the-kluctl-webui/</link><pubDate>Tue, 12 Sep 2023 00:00:00 +0000</pubDate><guid>https://kluctl.io/blog/2023/09/12/introducing-the-kluctl-webui/</guid><description>This blog post serves as an introduction and a tutorial for the new Kluctl Webui, which marks the next milestone in the Kluctl Ecosystem. It gives you visibility and control over your Kluctl deployments, no matter if these happen through your local command line, a CI/CD pipeline or the Kluctl GitOps Controller.
The Webui has been released as part of the v2.21.0 release of Kluctl.
What is Kluctl? In case this is the first time you heard about Kluctl, lets take a few steps back and first give a short introduction what Kluctl actually is.</description></item><item><title>Managing many Helm Charts with Kluctl</title><link>https://kluctl.io/blog/2023/02/28/managing-many-helm-charts-with-kluctl/</link><pubDate>Tue, 28 Feb 2023 00:00:00 +0000</pubDate><guid>https://kluctl.io/blog/2023/02/28/managing-many-helm-charts-with-kluctl/</guid><description>If you are a DevOps engineer, SRA, a Homelab enthusiast or in any other comparable role that needs to manage Kubernetes deployments, you&amp;rsquo;ll probably have made the same journey that many others have gone. You started with plain YAML manifests deployed via kubectl and eventually found out about Helm and Kustomize.
Whatever tool you decide to go for, the next realisation is usually that Helm and Kustomize itself need to be managed as well.</description></item><item><title>Introducing the Template Controller and building GitOps Preview Environments</title><link>https://kluctl.io/blog/2022/12/28/template-controller/</link><pubDate>Wed, 28 Dec 2022 00:00:00 +0000</pubDate><guid>https://kluctl.io/blog/2022/12/28/template-controller/</guid><description>This blog post serves two purposes. The first one is to announce and present the Template Controller (Source). The second purpose is to demonstrate it by setting up a simple GitOps based Kubernetes deployment with dynamic preview environments.
The Template Controller The template-controller is a Kubernetes controller that is able to create arbitrary objects based on dynamic templates and arbitrary input objects. It is inspired by ArgoCD&amp;rsquo;s ApplicationSet, which is able to create dynamic ArgoCD Applications from a list of generators (e.</description></item><item><title>Templating in Kustomize with Kluctl style deploy and diff</title><link>https://kluctl.io/blog/2022/11/17/templating-and-diffs-with-kustomize/</link><pubDate>Thu, 17 Nov 2022 00:00:00 +0000</pubDate><guid>https://kluctl.io/blog/2022/11/17/templating-and-diffs-with-kustomize/</guid><description>Kustomize is currently one of the most used tools to organise Kubernetes manifests and the resulting deployments. As of the Kustomize website, &amp;ldquo;Kustomize introduces a template-free way to customize application configuration that simplifies the use of off-the-shelf applications.&amp;rdquo;
This says it very clear: Kustomize is template-free. The reasoning why Kustomize does not leverage templating and also will never do so is very reasonable and easy to understand. It tries to avoid the potential overload and complexity that comes with templating.</description></item><item><title>Multiple Environments with Flux and Kluctl</title><link>https://kluctl.io/blog/2022/06/03/multiple-environments-with-flux-and-kluctl/</link><pubDate>Fri, 03 Jun 2022 00:00:00 +0000</pubDate><guid>https://kluctl.io/blog/2022/06/03/multiple-environments-with-flux-and-kluctl/</guid><description>Please note that the information in this blog post is outdated. Kluctl does not integrate into Flux anymore and instead provides an independent Kluctl Controller. Most projects that have server-side components usually need to be deployed multiple times, at least if you don&amp;rsquo;t want to break things for your users all the time. This means, that there is not only one single &amp;ldquo;prod&amp;rdquo; environment, but also something like &amp;ldquo;test&amp;rdquo; or &amp;ldquo;staging&amp;rdquo; environments.</description></item><item><title>Rethinking Kubernetes Configuration Management</title><link>https://kluctl.io/blog/2022/05/16/rethinking-kubernetes-configuration-management/</link><pubDate>Mon, 16 May 2022 00:00:00 +0000</pubDate><guid>https://kluctl.io/blog/2022/05/16/rethinking-kubernetes-configuration-management/</guid><description>One of the big advantages of Kubernetes is its declarative nature when it comes to deployed resources. You define what state you expect, apply it to Kubernetes and then let it figure out how to get to that state.
At first, this sounds like a big win, which it actually is. It however doesn’t take long for beginners to realize that simply writing yamls and applying them via “kubectl apply” is not enough.</description></item><item><title>Kluctl and Flux</title><link>https://kluctl.io/blog/2022/05/11/kluctl-and-flux/</link><pubDate>Wed, 11 May 2022 00:00:00 +0000</pubDate><guid>https://kluctl.io/blog/2022/05/11/kluctl-and-flux/</guid><description>Please note that the information in this blog post is outdated. Kluctl does not integrate into Flux anymore and instead provides an independent Kluctl Controller. We&amp;rsquo;re very happy to announce that Kluctl can from now on be used together with Flux. This will allow you to combine the workflows and features advertised by Kluctl with GitOps style continuous delivery.
via GIPHY
GitOps vs Kluctl One of the first questions that we usually get when introducing Kluctl to someone is something like: &amp;ldquo;Why not GitOps?</description></item></channel></rss>