<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gatekeeper on Support Tools</title><link>https://support.tools/tags/gatekeeper/</link><description>Recent content in Gatekeeper on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 15 Oct 2026 00:00:00 -0500</lastBuildDate><atom:link href="https://support.tools/tags/gatekeeper/index.xml" rel="self" type="application/rss+xml"/><item><title>OPA Gatekeeper: Production-Grade Policy Enforcement for Kubernetes Clusters</title><link>https://support.tools/opa-gatekeeper-policy-enforcement-kubernetes-production/</link><pubDate>Thu, 15 Oct 2026 00:00:00 -0500</pubDate><guid>https://support.tools/opa-gatekeeper-policy-enforcement-kubernetes-production/</guid><description>&lt;p&gt;Open Policy Agent (OPA) Gatekeeper has become the industry standard for policy-based control in Kubernetes environments. As a CNCF graduated project, Gatekeeper extends OPA&amp;rsquo;s policy-as-code capabilities with Kubernetes-native resources, providing declarative admission control that enforces organizational policies across clusters.&lt;/p&gt;&#10;&lt;p&gt;In this comprehensive guide, we&amp;rsquo;ll explore enterprise-grade Gatekeeper implementations, covering constraint template development, mutation policies, audit frameworks, and integration patterns that have proven effective in managing thousands of workloads across multi-tenant environments.&lt;/p&gt;</description></item><item><title>How to use OPA Gatekeeper to only allow images from a private registry.</title><link>https://support.tools/post/opa-gatekeeper-allow-images-from-private-registry/</link><pubDate>Fri, 11 Jun 2021 01:11:00 +0000</pubDate><guid>https://support.tools/post/opa-gatekeeper-allow-images-from-private-registry/</guid><description>&lt;p&gt;By default, Kubernetes will pull from Docker Hub unless the deployment requests a fully qualified path. For example, if you deploy a pod with the image &lt;code&gt;rancherlabs/swiss-army-knife,&lt;/code&gt; Kubernetes will default &lt;code&gt;index.docker.io/rancherlabs/swiss-army-knife.&lt;/code&gt; This is works for environments that can pull images from the internet. But in environments that don&amp;rsquo;t have internet access or if your security team requires all images to be scanned before being deployed. To solve this issue, you&amp;rsquo;ll need to instruct your application teams to update to use a private registry IE &lt;code&gt;private.example.com/rancherlabs/swiss-army-knife.&lt;/code&gt;, But there is always a chance that an application team forgets to change their image path in their code. Now you have pods stuck in &lt;code&gt;imagepullbackoff.&lt;/code&gt; To prevent this kind of issue, we will set up OPA Gatekeeper to block all deployment requests that are missing our private registry IE &lt;code&gt;private.example.com.&lt;/code&gt;&lt;/p&gt;</description></item><item><title>How to use OPA Gatekeeper to require a label on all namespaces.</title><link>https://support.tools/post/opa-gatekeeper-require-labels/</link><pubDate>Fri, 11 Jun 2021 01:11:00 +0000</pubDate><guid>https://support.tools/post/opa-gatekeeper-require-labels/</guid><description>&lt;p&gt;By default, Kubernetes will create namespaces without any labels. This can tracking the owner of the namespace difcult. Also, by having all namespaces labeled. You can use labels for running show-back and charge-back reports based on owner labels.&lt;/p&gt;</description></item></channel></rss>