Ratify
Is a verification engine as a binary executable and on Kubernetes which enables verification of artifact security metadata and admits for deployment only those that comply with policies you create.
WARNING: This is not considered production-grade code by its developers, nor is it "supported" software.
Table of Contents
Community meetings
- Agenda: https://hackmd.io/ABueHjizRz2iFQpWnQrnNA
- We hold a weekly Ratify community meeting with alternating times to accommodate more time zones. Series #1 Wed 4:30-5:30pm Series #2 Wed 1-2pm Get Ratify Community Meeting Calendar here
- We meet regularly to discuss and prioritize issues. The meeting may get cancelled due to holidays, all cancellation will be posted to meeting notes prior to the meeting.
- Reach out on Slack at cloud-native.slack.com#ratify. If you're not already a member of cloud-native slack channel, first add yourself here.
Pull Request Review Series
- We hold a weekly Ratify Pull Request Review Series on Mondays 5-6 pm PST.
- People are able to use this time to walk through any Pull Requests and seek feedback from others in the Community. If there are no PR to review, the meeting will be cancelled during that week.
- Reach out on Slack if you want to reserve a session for review or during our weekly community meetings.
Quick Start
Try out ratify in Kubernetes through Gatekeeper as the admission controller.
Prerequisites:
- Kubernetes v1.20 or higher
- OPA Gatekeeper v3.10 or higher
Step 1: Setup Gatekeeper with external data
NOTE: If you have added Helm repository for Gatekeeper and Ratify, you can update them by executing
helm repo updatebefore installation.
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 validatingWebhookTimeoutSeconds=5 \
--set mutatingWebhookTimeoutSeconds=2NOTE:
validatingWebhookTimeoutSecondsandmutationWebhookTimeoutSecondsincreased from 3 to 5 and 1 to 2 respectively, so all Ratify operations complete in complex scenarios. See discussion here to remove this requirement. Kubernetes v1.20 or higher is REQUIRED to increase timeout. Timeout is configurable in helm chart underprovider.timeoutsection.
Step 2: Deploy ratify on gatekeeper in the default namespace.
- Option 1: Install the last released version of Ratify
Note: if the crt/key/cabundle are NOT set under provider.tls in values.yaml, helm would generate a CA certificate and server key/certificate for you.
helm repo add ratify https://deislabs.github.io/ratify
# download the notary verification certificate
curl -sSLO https://raw.githubusercontent.com/deislabs/ratify/main/test/testdata/notary.crt
helm install ratify \
ratify/ratify --atomic \
--namespace gatekeeper-system \
--set-file notaryCert=./notary.crt- Option 2: Install ratify with charts from your local branch.
Note: Latest chart in main may not be compatible with the last released version of ratify image, learn more about weekly dev builds here
git clone https://github.com/deislabs/ratify.git
cd ratify
helm install ratify \
./charts/ratify --atomic \
--namespace gatekeeper-system \
--set-file notaryCert=./test/testdata/notary.crtStep 3: See Ratify in action
- Deploy a
democonstraint.
kubectl apply -f https://deislabs.github.io/ratify/library/default/template.yaml
kubectl apply -f https://deislabs.github.io/ratify/library/default/samples/constraint.yaml
Once the installation is completed, you can test the deployment of an image that is signed using Notary V2 solution.
- This will successfully create the pod
demo
kubectl run demo --image=wabbitnetworks.azurecr.io/test/notary-image:signed
kubectl get pods demoOptionally you can see the output of the pod logs via: kubectl logs demo
- Now deploy an unsigned image
kubectl run demo1 --image=wabbitnetworks.azurecr.io/test/notary-image:unsignedYou will see a deny message from Gatekeeper denying the request to create it as the image doesn't have any signatures.
Error from server (Forbidden): admission webhook "validation.gatekeeper.sh" denied the request: [ratify-constraint] Subject failed verification: wabbitnetworks.azurecr.io/test/net-monitor:unsignedYou just validated the container images in your k8s cluster!
Step 4: Uninstall Ratify
Notes: Helm does NOT support upgrading CRDs, so uninstalling Ratify will require you to delete the CRDs manually. Otherwise, you might fail to install CRDs of newer versions when installing Ratify.
kubectl delete -f https://deislabs.github.io/ratify/library/default/template.yaml
kubectl delete -f https://deislabs.github.io/ratify/library/default/samples/constraint.yaml
helm delete ratify --namespace gatekeeper-system
kubectl delete crd stores.config.ratify.deislabs.io verifiers.config.ratify.deislabs.io certificatestores.config.ratify.deislabs.ioNotes
If the image reference provided resolves to an OCI Index or a Docker Manifest List, validation will occur ONLY at the index or manifest list level. Ratify currently does NOT support image validation based on automatic platform selection. For more information, see this issue.
Documents
The docs folder contains the beginnings of a formal specification for the Reference Artifact Verification framework and its plugin model.
Meeting notes for weekly project syncs can be found here
Code of Conduct
This project has adopted the Microsoft Open Source Code of Conduct.
For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
Release Management
The Ratify release process is defined in RELEASES.md.
Licensing
This project is released under theΒ Apache-2.0 License.
Trademark
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.