Nicolas Fränkel 🇺🇦🇬🇪<p>This week’s post is the third and final in my series about running tests on <a href="https://mastodon.top/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Kubernetes</span></a> for each pull request. In the 1st post, I described the app and how to test locally using <a href="https://mastodon.top/tags/Testcontainers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Testcontainers</span></a> and in a <a href="https://mastodon.top/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GitHub</span></a> workflow. The second post focused on setting up <a href="https://mastodon.top/tags/GKE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GKE</span></a> and running end-to-end tests on Kubernetes.</p><p>In this post, I’ll show how to benefit from the best of both worlds with <a href="https://mastodon.top/tags/vCluster" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>vCluster</span></a>: a single cluster with testing from each PR in complete isolation from others.</p><p><a href="https://blog.frankel.ch/pr-testing-kubernetes/3/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.frankel.ch/pr-testing-kub</span><span class="invisible">ernetes/3/</span></a></p>