-
Notifications
You must be signed in to change notification settings - Fork 350
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
ApisixTls status not updated #1221
Comments
Ehh, my bad, it works as expected, the status tricked me, it is not updated. |
Do you mean the status of the ApisixTls resource is not updated? |
Yes @tao12345666333 |
We expected that all status should be updated correctly, so I reopened this issue |
Will reproduce when I'm free, if this is confirmed we can fix it Can you provide a minimal complete reproduction steps if you are interested? |
@tao12345666333 sure, I will on the weekend if that's fine, don't have time right now |
Here is how to reproduce: create namespace and the ApisixTls:
check the ApisixTls status:
ingress controller logs (secret not found):
wait a few seconds, then create the tls secret
ingress controller logs (only healthcheck, no error):
apisix logs (ssl resource created successfully in apisix):
Check the ApisixTls status again, not updated:
|
thanks! |
Would you like to try to fix this problem? There is a |
Yes, sure,I'll try. |
Thanks for your confirmation, then I think this issue can be closed, right? |
Also, I thought maybe we should create a patch for 1.5.0 to use . You can try |
I won't really have time for this, sorry. |
Don't worry, thanks for your contribution |
Issue description
I use cert manager to generate certificates and create the
Certificate
andApisixTls
resources at the same time. Cert-manager needs some time to request the certificate, so when apisix-ingress-controller tries to find the cert secret it doesn't exist yet. The problem is apisix-ingress-controller won't retry to find the secret, so we are stucked. I know it is documented here that the secret should exist when we create the ApisixTls resource, but with a retry mechanism it would be much more relieable.Edit: as I see, there is a retry rule in apisix-ingress-controller, but in this case it doesn't seem to retry. Maybe because of the
ResourceSyncAborted
status reason?Environment
Minimal test code / Steps to reproduce
Install cert-manager and apisix-ingress-controller, and
create the following:
Actual result
Error log
Expected result
No response
The text was updated successfully, but these errors were encountered: