Skip to content
#

cosign

Here are 27 public repositories matching this topic...

zarf
YrrepNoj
YrrepNoj commented May 26, 2022

If someone were to accidently zarf init --components=k3s twice (it doesn't have to be back-to-back, just before Zarf destroys the first cluster), weird stuff happens that Zarf doesn't handle in the best way.

One of the files that gets copied to the host during the installation of the k3s component is an 'empty-file' that gets placed in the /root/.kube/config. Since k3s/zarf is already runni

marcofranssen
marcofranssen commented Sep 28, 2021

By implementing a proxying command we can invoke vault cli options via spiffe-vault directly.

e.g.

./spiffe-vault proxy 'vault read transit/keys/cosign'

as opposed to running

eval "$(./spiffe-vault auth -role local)"
vault read transit/keys/cosign

This way we will never have to export the token within the current shell.

enhancement good first issue help wanted

Sign your artifacts, source code or container images using Sigstore tools, Save the Signatures you want to use, and Validate & Control the deployments to allow only the known Sources based on Signatures, Maintainers & other payloads automatically.

  • Updated Jun 15, 2022
  • Go

Improve this page

Add a description, image, and links to the cosign topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the cosign topic, visit your repo's landing page and select "manage topics."

Learn more