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
Gloo failing with v1.Secret: unknown field "tls.crt" / "ca.crt" #3652
Comments
I have recreated this following doc here: https://cert-manager.io/docs/installation/ With validation enabled:
Without validation:
|
If there are 2 failures and 1 is an Inja failure then only the Inja failure is reported. Also. even though there is a rejection the proxy object is still returned.
|
Any updates on this? |
Hello, sorry for the delayed response. The issue is happening here. Our secret converter does not currently handle the optional |
Hi Guys, can we get this going? Happy to submit a PR. |
A PR would be awesome, and we'd be happy to help. I linked above to the offending code. |
Hi guys, thanks for offering to jump on a PR, but I think someone on the Solo side will be starting on this task sometime this week. |
@kdorosh That is great news. Unfortunately (or fortunately in this case), I was side-tracked by some other issues. |
Describe the bug
Gloo crashes with the following error message:
cert-manager
creates a Kubernetes secret in the following format:To Reproduce
Steps to reproduce the behavior:
Expected behavior
A working integration with cert-manager.
Additional context
Add any other context about the problem here, e.g.
The text was updated successfully, but these errors were encountered: