<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Validation on Atlas</title><link>https://www.javiercd.es/en/tags/validation/</link><description>Recent content in Validation on Atlas</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 26 Jul 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://www.javiercd.es/en/tags/validation/index.xml" rel="self" type="application/rss+xml"/><item><title>Installing Kong Ingress Controller (KIC)</title><link>https://www.javiercd.es/en/posts/kong/03-instalacion-kic/03-instalacion-kic/</link><pubDate>Sun, 26 Jul 2026 00:00:00 +0200</pubDate><guid>https://www.javiercd.es/en/posts/kong/03-instalacion-kic/03-instalacion-kic/</guid><description>&lt;p&gt;In this article, we will move from theory to a real deployment. The goal is to install &lt;strong&gt;Kong Ingress Controller (KIC)&lt;/strong&gt; in a Kubernetes cluster, verify that &lt;strong&gt;Kong Gateway&lt;/strong&gt; is working properly, and prepare the external exposure of the proxy so that we can publish applications from the cluster itself.&lt;/p&gt;
&lt;p&gt;To keep the lab simple, I will use a single virtual machine created with &lt;strong&gt;Vagrant&lt;/strong&gt; on which I will run a &lt;strong&gt;k3s&lt;/strong&gt; cluster. This choice does not change the way Kong works, but it allows us to focus on what really matters: what KIC installs, why the proxy service initially appears in &lt;code&gt;Pending&lt;/code&gt;, and how to solve that with &lt;strong&gt;MetalLB&lt;/strong&gt;.&lt;/p&gt;</description></item></channel></rss>