<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Ipsec - Tag - Lorenzo's Blog</title><link>https://www.k8s.it/tags/ipsec/</link><description>Ipsec - Tag - Lorenzo's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 11 Aug 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://www.k8s.it/tags/ipsec/" rel="self" type="application/rss+xml"/><item><title>Kubernetes VPN Strongswan — IPsec with LDAP Auth</title><link>https://www.k8s.it/posts/kubernetes-strongswan/</link><pubDate>Tue, 11 Aug 2020 00:00:00 +0000</pubDate><author>Lorenzo Girardi</author><guid>https://www.k8s.it/posts/kubernetes-strongswan/</guid><description><![CDATA[<div class="featured-image">
                <img src="/images/kubernetes-strongswan/vpn_diagram.jpg" referrerpolicy="no-referrer">
            </div><h2 id="how-to-manage-vpn-in-a-kubernetes-environment">How to Manage VPN in a Kubernetes Environment</h2>
<p>Traditional IPsec-XAuth VPN manages credentials in flat files. Adding a user means editing a file and redeploying. Removing a user means the same. In a Kubernetes environment, that&rsquo;s not acceptable.</p>
<p>This implementation integrates Strongswan with LDAP, turning VPN access into a standard directory operation — the same system that manages every other credential in the organization.</p>
<p></p>]]></description></item></channel></rss>