<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cert-Manager on Besmir Zanaj</title><link>https://cloudalbania.com/tags/cert-manager/</link><description>Recent content in Cert-Manager on Besmir Zanaj</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 12 Dec 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://cloudalbania.com/tags/cert-manager/index.xml" rel="self" type="application/rss+xml"/><item><title>Replacing F5 BIG-IP with NGINX Ingress and MetalLB</title><link>https://cloudalbania.com/2024-12-replacing-f5-big-ip-with-nginx-ingress-and-metallb/</link><pubDate>Thu, 12 Dec 2024 00:00:00 +0000</pubDate><guid>https://cloudalbania.com/2024-12-replacing-f5-big-ip-with-nginx-ingress-and-metallb/</guid><description>What had to be replaced What the existing setup looks like Picking a replacement The lab NGINX Ingress controller MetalLB for the VIP Monitoring, and why it does not answer the monitors requirement TLS termination with cert-manager external-dns, and a way to delete production High availability, active/standby, and what MetalLB actually gives you Getting to production throughput Converting F5 SCF files to Ingress objects What is easy to migrate and what is not Cutover difficulties What the requirements left out Update, 2026: I would use Gateway API now What had to be replaced The job was to get off the F5 appliances and onto something we ran ourselves.</description></item></channel></rss>