Skip to content
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

Notation verification fails due to Certificate Store not found after v1.1 ratify update #1269

Open
1 task
susanshi opened this issue Jan 19, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@susanshi
Copy link
Collaborator

What happened in your environment?

This issue is created to help customer mitigate the CRD breaking change for upgrade to ratify v1.1

Certificate Store is a namespaced CR. We have made a fix in this release so that Certificate Store CR can be uniquely referenced by Verifier CR.

No action item if you are using the default ratify helm chart.
If you maintain custom Ratify chart or have manually applied CertificateStore CR,
please edit the Verifier CR to append the namespace of the Certificate Store. See notation verifier example here.

What did you expect to happen?

No response

What version of Kubernetes are you running?

No response

What version of Ratify are you running?

v1.1

Anything else you would like to add?

No response

Are you willing to submit PRs to contribute to this bug fix?

  • Yes, I am willing to implement it.
@susanshi susanshi added bug Something isn't working triage Needs investigation labels Jan 19, 2024
@luisdlp luisdlp self-assigned this Jan 23, 2024
@luisdlp luisdlp removed the triage Needs investigation label Jan 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants