<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>F5 on Network Doodles</title><link>https://networkdoodles.com/tags/f5/</link><description>Recent content in F5 on Network Doodles</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 02 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://networkdoodles.com/tags/f5/index.xml" rel="self" type="application/rss+xml"/><item><title>Managing TLS Certificates Using Ansible and Let’s Encrypt! PART 2.2:</title><link>https://networkdoodles.com/posts/letsencrypt-part2_2/</link><pubDate>Mon, 02 Nov 2026 00:00:00 +0000</pubDate><guid>https://networkdoodles.com/posts/letsencrypt-part2_2/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Continuing from &lt;a href="https://networkdoodles.com/posts/letsencrypt-part2_1/"&gt;Part 2.1&lt;/a&gt;, where we pushed certificates to a Cisco ASA, this post does the same thing for &lt;strong&gt;F5 BIG-IP&lt;/strong&gt;. The certificates still come from the &lt;code&gt;cert-store&lt;/code&gt; repository we built in &lt;a href="https://networkdoodles.com/posts/letsencrypt-part2/"&gt;Part 2&lt;/a&gt;, and the playbook still runs from AWX/AAP. What&amp;rsquo;s new is a playbook that uploads the certificate, key and chain to the F5 and builds (or updates) a client SSL profile for each one.&lt;/p&gt;</description></item></channel></rss>