-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no bundle found in referrers #179
Comments
Hi @julien-michaud! Thank you for the report. I'm sorry for the delayed response. I don't see anything obviously wrong with your configuration, so I'd like to gather a bit more information to assess the problem. Could you please confirm that you've followed the instructions here to install the latest version of the two helm charts ( Do you have logs from your GitHub Actions workflow run that indicate that the attestation was successfully pushed to your registry? And can you verify that the image digest in the actions run matches the digest that you are running in Kubernetes? |
I think I did everything correctly 🤷 Here are the chart installed on my cluster:
controller logs when started
The trustroot object installed:
the cluster image policy:
the attestation created by the reusable workflow
controller logs when trying to create a pod:
|
Hello 👋
We are signing our docker images with the actions/attest-build-provenance@v1 Action.
We are trying to use the controller from this repository to verify images in our k8s clusters but we are having this issue when submitting new pods:
Error from server (BadRequest): error when creating "pod.yaml": admission webhook "policy.sigstore.dev" denied the request: validation failed: failed policy: github-policy: spec.template.spec.containers[0].image europe-docker.pkg.dev/project/company-prod/kube/mp/tiny-developer-tools@sha256:abd5c78061356d3f9b14475a1afd11c68baf6c89c03a036b442ef7d520556fcd no bundle found in referrers
Is the problem on my end ?
snippet of the workflow creating, pushing and signing the image
Thanks
probably related to this issue sigstore/policy-controller#1406
The text was updated successfully, but these errors were encountered: