-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Secretes are not automatically loaded #995
Comments
I think this was fixed by #991 |
@jerryjxj please update the image to |
Closing. Please reopen if the issue persists after the update |
Did someone verify whether this issue is fixed? iirc, it isn't. need to re-check soon. |
@bechtoldt did you use 0.9-beta.12? |
yeah, it works! |
I was able to reproduce this both on
When the default ingress fake cert is served, recreating only the ingress controller always helped (when the secret remained the same). So probably some kind of race condition, since it does not happen every time? Logs from
|
When I created a ingress and after for a while, then I created a screte needed by ingress. The certificate (in the secret) was not reloaded.
Refer to issue 947
The text was updated successfully, but these errors were encountered: