gatekeeper-policy-manager
Из публичных источниковПростой в использовании веб-менеджер политик OPA Gatekeeper
Машинный перевод · Показать оригинал
A simple to use web-based OPA Gatekeeper policy manager
Обзор
- dashboard
- fury
- gatekeeper
- k8s
- kubernetes
- kustomize
- opa
- policies
- rego
- ui
- web
- webapp
Установка
Команды только показываются, маркетплейс их не выполняет. Сверяйтесь с официальной документацией.- Официальный сайтИз публичных источниковиз метаданных каталогаsighup.io/ ↗
- Файлы официального релизаИз публичных источниковиз последнего официального релизаgithub.com/sighupio/gatekeeper-policy-manager/releases/tag/v2.1.2 ↗
- Сборка из исходниковИз публичных источниковиз метаданных каталога
Сборка из исходников: проверенного рецепта сборки нет — следуйте инструкциям репозитория.
github.com/sighupio/gatekeeper-policy-manager ↗
Совместимость
«Неизвестно» значит, что доказательств не найдено, а не что продукт несовместим.| Платформа | Статус | Архитектура | Доказательство | Уверенность |
|---|---|---|---|---|
| Web browser | Неизвестно | — | — | — |
| Server / self-hosted | Неизвестно | — | — | — |
| Container (OCI) | Неизвестно | — | — | — |
Релизы
проверено 30 окт. 2026 г.Файлы версии 2.1.2
| Файл | Платформа | Размер | SHA-256 | Скачать из официального источника |
|---|---|---|---|---|
| gatekeeper-policy-manager-v2.1.2.tar.gz | Неизвестно | 6,2 KB | c3bc7723affd… | Официальный источник ↗ |
| sha256sum.txt | контрольные суммы | 106 B | 5d9f5c1755a3… | Официальный источник ↗ |
| md5sum.txt | другое | 74 B | 263b5e90f299… | Официальный источник ↗ |
История релизов
- v2.1.121 окт. 2026 г.Официальный источник ↗
- v2.1.014 сент. 2026 г.Официальный источник ↗
- v2.0.019 авг. 2026 г.Официальный источник ↗
- v1.1.24 авг. 2026 г.Официальный источник ↗
- v1.1.118 мар. 2026 г.Официальный источник ↗
- v1.1.025 авг. 2025 г.Официальный источник ↗
- v1.0.1417 июн. 2025 г.Официальный источник ↗
Профиль качества
алгоритм quality-v1.0 · оценено 16 окт. 2026 г.Составляющие оценки
Лицензия
BSD-3-ClauseЭто статус политики каталога, а не юридическое заключение.
Источники
Отзывы
Отзывов пока нет.
Альтернативы
README
Из sighupio/gatekeeper-policy-manager · лицензия BSD-3-Clause · загружено 30 окт. 2026 г.[GPM Release] [Helm Chart Release] [License]
Gatekeeper Policy Manager is a read-only web UI that shows the status of OPA Gatekeeper policies in a Kubernetes cluster.
The target Kubernetes cluster can be the same one where GPM runs, or a remote cluster that GPM connects to with a kubeconfig file. You can also run GPM locally on a client machine and connect to a remote cluster.
GPM lets you see in detail:
- Constraint Templates with their rego code.
- Constraints with their current status, violations, enforcement action, matches definitions, etc.
- Mutations defined and their details.
- Events emitted by OPA Gatekeeper (alpha feature).
- Gatekeeper Configuration custom resource values.
You can see some screenshots below ⤵.
Requirements
GPM needs OPA Gatekeeper in your cluster. It also needs some constraint templates and constraints. Without them, GPM has nothing to show.
[!TIP] You can deploy Gatekeeper to your cluster with the SIGHUP Distribution Policy Module (also open source).
Deploying GPM
Deploy using Kustomize
To deploy Gatekeeper Policy Manager to your cluster, apply the kustomization file with this command:
kubectl apply -k https://github.com/sighupio/gatekeeper-policy-manager
By default, this creates a deployment and a service named gatekeeper-policy-manager in the gatekeeper-system namespace. To configure more, see the kustomization.yaml file.
[!NOTE] GPM can run as a Pod in a Kubernetes cluster, or locally with a
kubeconfigfile. It autodetects the correct configuration.
If you did not configure an ingress, use port-forward to access the web UI:
kubectl -n gatekeeper-system port-forward svc/gatekeeper-policy-manager 8080:80
Then open http://127.0.0.1:8080 in your browser.
Deploy using Helm
You can also deploy GPM with the Helm chart.
First create a values file, for example my-values.yaml, with your custom values for the release. See the chart's readme and the default values.yaml for more information.
From v2.1.0 the chart is published as an OCI artifact on quay.io, next to the container image. There is no helm repo add step any more. You need Helm 3.8 or later, which supports OCI registries. Then execute:
helm upgrade --install --namespace gatekeeper-system --set image.tag=v2.1.2 --values my-values.yaml gatekeeper-policy-manager oci://quay.io/sighup/charts/gatekeeper-policy-manager --version 0.20.2
[!IMPORTANT] Replace
my-values.yamlwith the path to your values file, and--version 0.20.2with the chart version you want.
Running locally
You can also run GPM locally with Docker (or another container runtime) and a kubeconfig. If the kubeconfig file is at ~/.kube/config, run this command:
docker run -v ~/.kube/config:/home/nonroot/.kube/config -p 8080:8080 quay.io/sighup/gatekeeper-policy-manager:v2.1.2
Then open http://127.0.0.1:8080 in your browser.
You can also run the app binary directly. See the development section for more information.
Configuration
GPM is stateless. You configure it with environment variables. The most common ones are:
| Env Var Name | Description | Default |
|---|---|---|
GPM_LOG_LEVEL | Log level (DEBUG, INFO, WARN, ERROR) | INFO |
GPM_AUTH_ENABLED | Set to OIDC or JWT to protect GPM. | Anonymous |
KUBECONFIG | Path to a kubeconfig file. If you set it in a cluster, GPM uses it instead of the cluster's API. | $HOME/.kube/config |
For more information, read these documents:
- Configuration: all the environment variables, subpath deployment, and events RBAC.
- Authentication: OIDC login, or an authenticating proxy such as Pomerium.
- RBAC-aligned views: show each person only what their Kubernetes account can read.
- Multi-cluster support: one GPM for more than one cluster, and AWS IAM authentication.
Screenshots
Development
GPM is written in Go. It uses the Echo framework and renders the UI on the server with the standard
library's html/template, plus a small amount of Alpine.js for interactivity. There is no separate
frontend build.
Alpine.js is vendored as static/ssr/alpine.min.js. Its version is pinned in package.json so
Dependabot tracks it; after a bump, run mise run vendor-alpine to refresh the vendored file (the
check-alpine-version task, part of mise run lint, fails if the two drift).
To develop GPM, run these commands:
# Install the dependencies
$ go mod download
# Run the development server
$ GPM_LOG_LEVEL=DEBUG go run .
[!TIP] A Kubernetes cluster with OPA Gatekeeper deployed helps you debug the application.
Contributing
Let us know if you use GPM and which features you want. Create an issue here on GitHub 💪🏻
To contribute, pick one of the open issues and work on it. It is better to tell us first on the issue.
When you are happy with your work, open a Pull Request.
We try to stick to conventional commits when writing commit messages.