---
title: "Steve Lasker (@SteveLasker) | Hashnode"
description: "Steve Lasker (@SteveLasker) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@SteveLasker"
---

@SteveLasker

# Steve Lasker

@SteveLasker · Joined January 2022

## Comments

[Hi Rewanth, Thanks for the write-up as we're all looking to help users find secure solutions. Just a quick note that you're comparing Notary v1. Notary v2 was created, due to the limitations you've outlined. Which cosign chose to follow a subset of these requirements. Please see the scenarios and goals being implemented with Notary v2 for a current comparison. github.com/notaryproject/notaryproject/blob/main/requirements.md A walkthrough of Notary v2, with Kubernetes is available here: https://github.com/Azure/notation-azure-kv/blob/main/docs/nv2-sign-verify-aks.md Or, this post from Lachie: https://medium.com/@LachlanEvenson/container-signing-with-notary-v2-13dd425e95d6](https://hashnode.com/posts/cosign-with-kubernetes-ensure-integrity-of-images-before-deployment/61e0656ecb0ca175a18dc90d/comment/61e1d9eed546507ab03435a4)

Comment · Article · Jan 14, 2022 · [CoSign with Kubernetes: Ensure integrity of images before deployment](https://hashnode.com/posts/cosign-with-kubernetes-ensure-integrity-of-images-before-deployment/61e0656ecb0ca175a18dc90d)