Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/developer-guy/cosign-gatekeeper-provider
🔮 ✈️ to integrate OPA Gatekeeper's new ExternalData feature with cosign to determine whether the images are valid by verifying their signatures
https://github.com/developer-guy/cosign-gatekeeper-provider
cosign fulcio gatekeeper keyless opa rekor sigstore
Last synced: 2 months ago
JSON representation
🔮 ✈️ to integrate OPA Gatekeeper's new ExternalData feature with cosign to determine whether the images are valid by verifying their signatures
- Host: GitHub
- URL: https://github.com/developer-guy/cosign-gatekeeper-provider
- Owner: sigstore
- License: apache-2.0
- Created: 2021-11-20T06:06:10.000Z (about 3 years ago)
- Default Branch: main
- Last Pushed: 2024-04-02T21:10:25.000Z (8 months ago)
- Last Synced: 2024-10-07T00:02:13.074Z (2 months ago)
- Topics: cosign, fulcio, gatekeeper, keyless, opa, rekor, sigstore
- Language: Go
- Homepage:
- Size: 621 KB
- Stars: 76
- Watchers: 11
- Forks: 23
- Open Issues: 24
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-opa - Cosign Gatekeeper Provider - Cosign Provider a new provider of OPA Gatekeeper's ExternalData feature to verify container images (Kubernetes / Built with Wasm)
README
# cosign-gatekeeper-provider
To integrate [OPA Gatekeeper's new ExternalData feature](https://open-policy-agent.github.io/gatekeeper/website/docs/externaldata) with [cosign](https://github.com/sigstore/cosign) to determine whether the images are valid by verifying its signatures.
> This repo is meant for testing Gatekeeper external data feature. Do not use for production.
## Installation
- Deploy Gatekeeper with external data enabled (`--enable-external-data`)
```sh
helm repo add gatekeeper https://open-policy-agent.github.io/gatekeeper/charts
helm install gatekeeper/gatekeeper \
--name-template=gatekeeper \
--namespace gatekeeper-system --create-namespace \
--set enableExternalData=true \
--set controllerManager.dnsPolicy=ClusterFirst,audit.dnsPolicy=ClusterFirst \
--version 3.10.0
```
_Note: This repository is currently only working with Gatekeeper 3.10 and the `externalData` feature in `alpha`. There is an open issue to track the support of Gatekeeper 3.11 and `externalData` feature in `beta`: https://github.com/sigstore/cosign-gatekeeper-provider/issues/20._
Let's install the `cosign-gatekeeper-provider`:
- `kubectl apply -f manifest`
- `kubectl apply -f manifest/provider.yaml`
> Update `url` if it's not `http://cosign-gatekeeper-provider.cosign-gatekeeper-provider:8090` (default)
- `kubectl apply -f policy/template.yaml`
- `kubectl apply -f policy/constraint.yaml`
## Verification
To test this successfully, we should sign one of our images with [cosign](https://github.com/sigstore/cosign#installation) tool. So, let's do this first:
Generate key pair
```shell
$ cosign generate-key-pair
```
We have two files under `policy/examples`, one for valid manifest that contains signed image, the other is invalid. To do the same you should sign your image as I did:
```shell
$ crane copy alpine:latest devopps/alpine:signed
$ crane copy alpine:3.14 devopps/alpine:unsigned
$ cosign sign --key cosign.key devopps/signed:latest
```
So, once you are ready, let's apply these manifests one by one. It should allow deploying Pod for valid.yaml, and deny for the other one.